The IETF officially standardized UUID v7 in 2024, challenging ULID's reign as the go-to sortable ID. Here's what changed and why it matters for your infrastructure.
For years, developers faced a painful choice: use UUID v4 (completely random, but slow for databases) or use timestamp-based solutions that weren't standards. ULID became the indie darling because it did what needed doing: embed a timestamp into the first part of the ID, giving you both uniqueness and chronological ordering. This meant faster database inserts and URLs that didn't look like alphabet soup.
In 2024, the IETF officially published RFC 9562, introducing UUID v7. It does almost exactly what ULID does: embeds a timestamp into the ID itself. The difference isn't functional; it's institutional. UUID v7 is now the official standard, meaning it has the weight of formal specification behind it.
This is significant. When a major framework like Rails 8 starts using UUID v7 as its default option, developers face a real choice: keep using the proven indie solution (ULID) or adopt the newly official standard.
This isn't a trivial decision. Your choice ripples through your stack: database performance, URL generation, API consistency, and maintenance burden down the road. If you're building something new in 2024 or 2025, you're deciding between:
We help businesses architect this decision into your database schema from day one, so you don't end up retrofitting primary keys later.
Both ULID and UUID v7 solve the same core problem: they give you sortable IDs without the performance penalty of randomness. The question isn't whether sortable IDs matter (they do); it's whether you go with the proven indie approach or the newly standardized one.
For startups and small businesses building new infrastructure, this favors UUID v7. For teams already deep in ULID implementations, there's no urgent need to migrate. For everyone else: this is the moment to make the call as you build.
How WebKing runs this
We handle database architecture decisions at scale. UUID choice cascades through your entire stack: insert performance, URL beauty, API consistency, and long-term maintenance. Getting this right from day one saves rewrites later.
Sources
The Lab is original analysis by WebKing. We summarize and interpret developments from the sources above for industrial, commercial, and small business owners. Figures are reported as published by their sources.
More from the desk
The IETF officially published UUID v7 in 2024, challenging ULID's reign as the go-to sortable identifier. Here's what changed and what it means for your infrastructure.
Industrial and commercial businesses that aren't using AI tools for content creation and ad optimization are falling behind. Here's what's actually moving the needle.
A gaming platform's event processing system was drowning in consistency and latency problems until engineers rebuilt service boundaries. Here's what broke and how they fixed it.
