50b1a4d0-88a4-4d61-88ee-b5e28b31a4ab 5cc0e241-0acc-477d-a7ae-e65dd32f3a20 ee3238e6-b62a-41aa-a068-5a7a8f789df1 44cadf22-dc0c-40a0-987e-97c202f1f4f8 84d4b7d0-92a3-4c36-8d2d-c27c3e7a6716 caf11d7e-8c55-4c10-87d5-d0e448b06192 421190c4-ae27-475a-9411-65b90cbbab97 45c9114c-2675-442d-9c8c-0678dfe2b70b eea087d8-c2f0-46c5-8927-a4ddae3f8503 0e7e3ae9-f781-45a6-9f1a-140563bc3cf0
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.
