f02500d8-b713-4990-a305-e49759da567a 6fcb895c-5998-437a-a53c-bce135f378b3 f65c9b48-5dc8-425e-bfc7-ab363dc0f683 41aa524d-49f4-4557-8abe-99b4a906f3a8 02e90947-f7f8-4193-8cd9-105c6bdc039c 8d231769-db7b-4ea4-89ee-42065c14d102 d8b64443-52ed-49b1-80c5-9d81bed0857f b54c3a60-9c3e-4daf-8ff5-cc26304edf14 db4ae687-438b-4006-898e-5c2ea8296abe 7fc759c5-2903-464a-9a90-ef36cdfe5c7f
v4 vs v7, in short
UUID v4 is 122 bits of pure randomness with no ordering — great for opacity, poor for database indexes because inserts land in random places. UUID v7 puts a Unix millisecond timestamp in the leading 48 bits and fills the rest randomly, so identifiers generated later always sort after earlier ones, which keeps B-tree indexes append-mostly and far faster under heavy insert load.
