7515a364-7e34-4f59-9e1e-7fe9c9175f51 b47f1c74-f162-4af1-88b9-b15374b9de13 8e67ab18-4420-4a24-8b89-4135cd359ec4 395c3663-71ec-4e56-a9b7-cacc087ab57d a7598f7b-6456-4557-837b-77f4d4f9859b 1f7cb8d6-4e81-4a2e-918d-7b70d2b855af 06f051bf-de3b-4bea-b84d-78ebc73fb84c 3aa8794e-eda2-4da1-9d3b-3aa5f5da2914 1a15e8cc-5c48-43a9-8cc0-b6e05c2f59be 5cc0f0e0-cd70-47e7-9734-03e62996eea4
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.
