Why Design a unique ID generator in HLD? - Purpose & Use Cases

The Big Idea

What if your system could never mix up or repeat IDs, no matter how busy it gets?

The Scenario

Imagine you are running a small online store and you assign order numbers by writing them down on paper or using a simple spreadsheet. When multiple people take orders at the same time, it becomes confusing to keep track of which order got which number.

The Problem

Manually assigning IDs is slow and prone to mistakes. People can accidentally reuse numbers or skip some, causing confusion and errors in tracking orders. It also becomes impossible to handle many orders quickly or from different places at once.

The Solution

A unique ID generator automatically creates a new, never-before-used ID every time it is asked. This means no two orders or items share the same number, even if many requests come in at the same time from different places. It works fast and reliably without human mistakes.

Before vs After

✗ Before

order_id = last_order_id + 1  # manually incrementing

✓ After

order_id = unique_id_generator.get_next_id()  # automatic unique ID

What It Enables

It enables systems to handle millions of requests simultaneously without any ID conflicts or delays.

Real Life Example

When you post a photo on social media, a unique ID is generated for that post so it can be found, liked, or shared without confusion.

Key Takeaways

Manual ID assignment causes errors and slows down processes.

Unique ID generators create conflict-free, fast, and reliable IDs automatically.

This is essential for scaling systems that handle many users or transactions.

Practice

1. What is the primary purpose of a unique ID generator in a distributed system?

easy

A. To create identifiers that are distinct across all machines and time

B. To encrypt data for secure communication

C. To compress large files efficiently

D. To balance load between servers

Solution

1. Step 1: Understand the role of unique IDs

   Unique IDs ensure that each identifier is different from others, avoiding conflicts.

2. Step 2: Recognize distributed system needs

   In distributed systems, IDs must be unique across machines and time to prevent collisions.

3. Final Answer:

   To create identifiers that are distinct across all machines and time -> Option A

4. Quick Check:

   Unique ID purpose = distinct identifiers [OK]

Hint: Unique IDs prevent duplicates across systems [OK]

Common Mistakes:

• Confusing unique ID with encryption
• Thinking unique ID compresses data
• Mixing load balancing with ID generation

2. Which of the following is a common component in a unique ID generator design?

easy

A. Encryption key for data security

B. Load balancer to distribute requests

C. Compression algorithm for data size reduction

D. Sequence number to avoid collisions within the same timestamp

Solution

1. Step 1: Identify components of unique ID generators

   Common components include timestamp, machine identifier, and sequence number.

2. Step 2: Understand sequence number role

   Sequence numbers help generate multiple unique IDs within the same timestamp to avoid collisions.

3. Final Answer:

   Sequence number to avoid collisions within the same timestamp -> Option D

4. Quick Check:

   Sequence number = collision avoidance [OK]

Hint: Sequence numbers prevent same-time ID clashes [OK]

Common Mistakes:

• Confusing encryption with ID generation
• Thinking compression is part of ID design
• Mixing load balancing with ID components

3. Consider a unique ID generator that uses a 41-bit timestamp, 10-bit machine ID, and 12-bit sequence number. What is the maximum number of unique IDs it can generate per millisecond per machine?

medium

A. 8192

B. 1024

C. 4096

D. 2048

Solution

1. Step 1: Understand bit allocation for sequence number

   The sequence number uses 12 bits, so max IDs per millisecond = 2^12.

2. Step 2: Calculate 2^12

   2^12 = 4096 unique IDs per millisecond per machine.

3. Final Answer:

   4096 -> Option C

4. Quick Check:

   2^12 = 4096 [OK]

Hint: 2^sequence_bits = max IDs/ms [OK]

Common Mistakes:

• Using machine ID bits instead of sequence bits
• Calculating 2^10 or 2^11 instead of 2^12
• Confusing total bits with sequence bits

4. A unique ID generator uses a timestamp, machine ID, and sequence number. If two machines generate IDs at the exact same millisecond with the same sequence number, what is the likely cause of duplicate IDs?

medium

A. Machine IDs are not unique or not included in the ID

B. Timestamp is too large

C. Sequence number is too long

D. The system uses encryption

Solution

1. Step 1: Analyze ID components for uniqueness

   Machine ID differentiates IDs from different machines at the same time.

2. Step 2: Identify cause of duplicates

   If machine IDs are missing or not unique, IDs from different machines can collide.

3. Final Answer:

   Machine IDs are not unique or not included in the ID -> Option A

4. Quick Check:

   Missing unique machine ID = duplicates [OK]

Hint: Unique machine ID prevents cross-machine duplicates [OK]

Common Mistakes:

• Blaming timestamp size for duplicates
• Thinking longer sequence number causes duplicates
• Confusing encryption with ID uniqueness

5. You need to design a unique ID generator for a global system with thousands of machines generating millions of IDs per second. Which design choice best ensures scalability and uniqueness?

hard

A. Generate random 64-bit numbers without coordination

B. Use a 64-bit ID combining timestamp, machine ID, and sequence number with synchronized clocks

C. Use only timestamp-based IDs without machine info

D. Assign IDs sequentially from a central server

Solution

1. Step 1: Consider scalability and uniqueness needs

   Global scale requires IDs unique across machines and time, with high throughput.

2. Step 2: Evaluate design options

   Combining timestamp, machine ID, and sequence number in 64 bits with synchronized clocks ensures uniqueness and scalability.

3. Step 3: Reject other options

   Random IDs risk collisions; timestamp-only lacks machine uniqueness; central server causes bottleneck.

4. Final Answer:

   Use a 64-bit ID combining timestamp, machine ID, and sequence number with synchronized clocks -> Option B

5. Quick Check:

   64-bit composite ID = scalable unique IDs [OK]

Hint: Combine time, machine, sequence for scalable unique IDs [OK]

Common Mistakes:

• Relying on random IDs risking collisions
• Ignoring machine ID causing duplicates
• Using central server causing bottlenecks