Yes — and it’s a valid choice with trade-offs. Pros: (1) generated client-side, no server coordination; (2) not sequentially guessable (URL security); (3) globally unique across sharded databases. Cons: (1) 16 bytes vs 4-8 for a sequential integer; (2) UUIDv4 causes B-tree index fragmentation from random insert order. Use UUIDv7 to eliminate the fragmentation issue — v7’s timestamp prefix makes inserts append-mostly. For high-traffic databases, benchmark UUIDv7 vs sequential ID vs Snowflake-style IDs. For most applications, UUIDv7 primary keys are the right modern default. Generate them with the UUID generator.
All questions