Server timestamps in Firebase - Step-by-Step Execution

Process Flow - Server timestamps

Client sends data with timestamp request

↓

Server receives data

↓

Server replaces placeholder with current time

↓

Server stores data with accurate timestamp

↓

Client reads stored data with server timestamp

The client sends data requesting a server timestamp. The server replaces the placeholder with the current time, stores it, and the client reads the accurate timestamp.

Execution Sample

Firebase

docRef.set({ createdAt: firebase.firestore.FieldValue.serverTimestamp() })

This code saves data with a server-generated timestamp to ensure accurate time.

Process Table

Step	Action	Client Data	Server Processing	Stored Data
1	Client prepares data with serverTimestamp placeholder	{ createdAt: serverTimestamp() }	None yet	None yet
2	Client sends data to server	{ createdAt: serverTimestamp() }	Received data with placeholder	None yet
3	Server replaces placeholder with current time	{ createdAt: serverTimestamp() }	Replaced with actual timestamp e.g. 2024-06-01T12:00:00Z	Stored with timestamp 2024-06-01T12:00:00Z
4	Client reads stored data	None	None	{ createdAt: "2024-06-01T12:00:00Z" }

💡 Execution stops after client reads the stored data with accurate server timestamp.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
createdAt	undefined	serverTimestamp()	serverTimestamp()	2024-06-01T12:00:00Z	2024-06-01T12:00:00Z

Key Moments - 2 Insights

Why does the client send a placeholder instead of the actual timestamp?

Because the client clock may be inaccurate, the placeholder tells the server to insert its own current time, ensuring the timestamp is reliable (see execution_table step 1 and 3).

When does the actual timestamp get assigned?

The server assigns the actual timestamp when it processes the data, replacing the placeholder before storing (see execution_table step 3).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'createdAt' after step 2?

A Actual timestamp like 2024-06-01T12:00:00Z

B undefined

C serverTimestamp() placeholder

D null

💡 Hint

Check the 'Client Data' column at step 2 in the execution_table.

At which step does the server replace the placeholder with the actual timestamp?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Server Processing' column in the execution_table.

If the client clock was used instead of serverTimestamp(), what would change in the execution_table?

A The placeholder would be replaced earlier at step 1

B The stored data would have an inaccurate timestamp

C The server would not replace the placeholder at step 3

D The client would not send any timestamp

💡 Hint

Think about why serverTimestamp() is used instead of client time, referencing variable_tracker.

Concept Snapshot

Server timestamps in Firebase:
- Use FieldValue.serverTimestamp() as a placeholder.
- Client sends data with this placeholder.
- Server replaces it with current time on receipt.
- Ensures accurate, consistent timestamps.
- Client reads stored data with real server time.

Full Transcript

Server timestamps in Firebase work by the client sending data with a special placeholder called serverTimestamp(). This placeholder tells the server to insert its own current time when it receives the data. The server replaces the placeholder with the actual timestamp and stores it. Later, when the client reads the data, it sees the accurate server-generated timestamp. This method avoids problems with incorrect client clocks and ensures consistent timing across all users.