December 9, 2025
Number wars: the ID fight club
Distributed ID Formats Are Architectural Commitments, Not Just Data Types
You thought IDs were just numbers — now the internet’s arguing over how they should look
TLDR: Choosing an ID format locks in long-term architecture, so it’s not “just a number.” Commenters clashed over time-based vs random IDs, praised a billion-offset hack, argued for checksums, and even roasted the writing—proof that tiny IDs cause big, real-world headaches.
Think IDs are just numbers? This post says those little strings become part of your system’s DNA, and the comments turned it into a full-blown reality show. The author warns that once IDs escape into URLs, dashboards, and support tools, changing them later is pain. Cue the crowd: mrkeen loved the “offset a billion” war story—old IDs below, new ones above—calling it gloriously hacky. Others argued over formats: random “UUIDs” (basically big unique codes) vs time-stamped ULIDs/UUIDv7, which sort nicely. theoli poked fun at a proposed “epoch shift,” joking that stretching a 12,000‑year clock to squeeze 50 more years is a chef’s kiss of absurdity. CGamesPlay wanted a built‑in checksum—think a safety digit to catch typos—instead of a bolt‑on afterthought. And then the spice: frutiger dragged the writing as “direct LLM” vibes, igniting a mini flame war about who’s more cringe—AI or engineers obsessing over number formats. Meanwhile orefalo rolled in with a spreadsheet showdown, throwing stats at the hype. Bottom line: once you pick an ID style, you’ve married it. The comment section agrees on one thing: numbers are easy until your system goes global—then even IDs need a PR manager. Expect strong opinions, memes, and side‑eye everywhere online.
Key Points
- •ID formats propagate across system boundaries and become architectural commitments.
- •Auto-increment IDs work for single databases but fail in distributed scenarios like sharding.
- •A practical migration workaround used a large offset (~1 billion) to avoid ID collisions across shards.
- •Distributed ID needs arise at inflection points: sharding, multi-region, microservices, and offline-first systems.
- •Common alternatives include UUIDv4 for coordination-free uniqueness and ULID/UUIDv7 for time-ordered IDs without central coordination.