Course contentsShow
← System Design
Lesson 1516 of 1,91937. Real-World System: URL ShortenerFree lesson

Counter-Based vs UUID Approaches

Compare simple counters (shorter, predictable) versus UUIDs (longer, globally unique) for different scale requirements.

Counter-Based vs UUID Approaches

What you'll learn: How to choose between simple counters and UUIDs for generating short URLs based on your scale and predictability requirements.


The Core Choice

When generating unique identifiers for short URLs, you face a fundamental tradeoff: counters produce the shortest, most efficient codes but are predictable and harder to distribute, while UUIDs offer global uniqueness and easy distribution but create much longer identifiers.

Counter-Based Approach

Think of a counter like a ticket dispenser at a deli—each request gets the next sequential number. For URL shorteners, this means:

  • Maximum compactness: A counter of 1 billion encoded in Base62 is just 6 characters (15ftgG)
  • Perfect collision avoidance: Sequential IDs never collide
  • Predictability risk: Users can guess abc123 → abc124, revealing information about your traffic volume
  • Distribution challenge: Requires coordination (like distributed ID generation from lesson 1511) to avoid duplicates across servers

UUID Approach

UUIDs are like randomly generated license plates with so many combinations that collisions are astronomically unlikely:

  • Instant distribution: No coordination needed—every server generates independently
  • Unpredictability: Random identifiers prevent enumeration attacks
  • Length penalty: Standard UUIDs are 36 characters; even truncated versions need ~16-22 characters to maintain low collision probability
  • Storage overhead: Longer URLs consume more database space and bandwidth

When to Use Each

Choose counters when you need maximum URL brevity, can handle centralized ID coordination, and predictability isn't a security concern (most URL shorteners).

Choose UUIDs when you need truly distributed generation without coordination, security through obscurity matters, or you're operating at extreme scale where multiple data centers must generate IDs independently.

Key Takeaway: Counter-based approaches optimize for the "short" in URL shortener but require coordination; UUIDs sacrifice brevity for simple, distributed generation—pick based on whether URL length or operational simplicity matters more to your requirements.