#uuid

Random UUID v4 primary keys bloated our video metadata index to 18 GB and pushed INSERT p99 to 30 ms

A UUID either records exactly when it was made or records nothing at all, and one hex digit decides which. The common v4 has no timestamp, so reading one off it is fiction.

UUID Generator API Generate UUID v1/v4/v5/v7 with bulk mode. Parse UUIDs to...

TL;DR — UUID v7 trie 13× plus vite que v4 en simulation B-tree (1M entrées), expose une empreinte...

Ever needed a unique identifier for a database record, a session token, or a file name? Generating...

UUID v7 vs v4 in PostgreSQL: why random UUIDs fragment B-tree indexes, how UUID v7 fixes it, benchmarks at 5M rows, and Drizzle ORM migration steps.

Three primary-key strategies for growing tables, benchmarked: integer, UUIDv4, UUIDv7 — and what each costs in insert speed.

How steganography solved the eternal UUID performance vs privacy dilemma in PostgreSQL

I generate a lot of UUIDs. Primary keys, cache keys, event IDs, request-trace IDs. Probably too many,...

Introduction: The Evolution of Unique Identifiers For decades, UUID v4 has been the...

UUID v7, ULID, KSUID — What's the Difference? I Implemented All Five A side-by-side...

If you are using UUID v4 as a primary key in a relational database, you are likely causing...