ObjectId and how it is generated in MongoDB - Step-by-Step Execution

Concept Flow - ObjectId and how it is generated

Start: Need unique ID

↓

Generate Timestamp (4 bytes)

↓

Generate Machine ID (3 bytes)

↓

Generate Process ID (2 bytes)

↓

Generate Counter (3 bytes)

↓

Combine all parts into 12-byte ObjectId

↓

Use ObjectId as unique document ID

ObjectId is created by combining time, machine, process, and counter parts to make a unique 12-byte ID.

Execution Sample

MongoDB

ObjectId() // generates a new unique 12-byte ID

This code creates a new ObjectId by combining timestamp, machine ID, process ID, and counter.

Execution Table

Step	Part Generated	Value (Hex)	Description
1	Timestamp	64E3A2F4	Current time in seconds since epoch (4 bytes)
2	Machine ID	5F1D3A	Unique machine identifier (3 bytes)
3	Process ID	1A2B	Current process identifier (2 bytes)
4	Counter	000001	Incrementing counter to avoid duplicates (3 bytes)
5	Combine	64E3A2F45F1D3A1A2B000001	Final 12-byte ObjectId

💡 All parts combined to form a unique ObjectId for document identification

Variable Tracker

Part	Initial	After Generation	Final
Timestamp	N/A	64E3A2F4	64E3A2F4
Machine ID	N/A	5F1D3A	5F1D3A
Process ID	N/A	1A2B	1A2B
Counter	0	1	1
ObjectId	N/A	N/A	64E3A2F45F1D3A1A2B000001

Key Moments - 3 Insights

Why does ObjectId include a timestamp?

The timestamp (step 1 in execution_table) ensures ObjectIds are roughly ordered by creation time and helps uniqueness.

What prevents two ObjectIds from being the same on the same machine and process?

The counter (step 4) increments for each ObjectId generated in the same second, avoiding duplicates.

Why is the machine ID part important?

The machine ID (step 2) ensures ObjectIds generated on different machines are unique even if timestamp and counter match.

Visual Quiz - 3 Questions

Look at the execution_table, what is the length in bytes of the Process ID part?

A 3 bytes

B 2 bytes

C 4 bytes

D 1 byte

💡 Hint

Check the 'Part Generated' and 'Value (Hex)' columns in the execution_table for Process ID

At which step is the counter value generated?

A Step 4

B Step 3

C Step 1

D Step 5

💡 Hint

Look for the row where 'Counter' is generated in the execution_table

If the machine ID was the same but the process ID changed, what would happen to the ObjectId?

A It would be the same

B Only the timestamp changes

C It would be completely different

D Only the counter changes

💡 Hint

Refer to how ObjectId combines machine ID and process ID in the execution_table

Concept Snapshot

ObjectId is a 12-byte unique ID.
It combines 4 parts: timestamp (4 bytes), machine ID (3 bytes), process ID (2 bytes), and counter (3 bytes).
Timestamp orders IDs by creation time.
Machine and process IDs ensure uniqueness across machines and processes.
Counter avoids duplicates within the same second.

Full Transcript

ObjectId in MongoDB is a unique identifier for documents. It is 12 bytes long and made by combining four parts: a 4-byte timestamp representing the current time, a 3-byte machine identifier unique to the computer, a 2-byte process ID for the running program, and a 3-byte counter that increments with each new ObjectId. This combination ensures each ObjectId is unique and roughly ordered by creation time. The timestamp helps sort documents by creation time. The machine and process IDs prevent collisions across different servers and processes. The counter prevents duplicates when multiple ObjectIds are created quickly on the same machine and process. This process creates a unique 12-byte hexadecimal string used as the document's ID.