23fce520-0b8a-46bc-8288-f8ab06c2b580 11f2dc60-592b-4d9d-9212-503849721641 555960e6-4cdb-4cc0-a944-13224815c5cc bbc91167-11e5-4c1b-b013-77f725b33d41 1a348f17-6f68-456c-a33d-d333030907b9 74da5503-3389-430a-990f-5d85db8fd8e7 aa732047-a70e-4ace-a054-a1653b19ba9d 20062529-ba12-4837-9e0b-d2a693d3b3a9 ccbbd7b4-d9b3-4f51-9789-e889ec9387b2 99f3b896-65d8-4935-ac5a-29474702e6df
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.
