alt Hacker NewsThe is article is about a solution in search of a problem, a classic premature optimization issue. UUIDv4 is perfectly fine for many use cases, including small databases. Performance argument must be considered when there’s a problem with performance on the horizon. Other considerations may be and very often superior to that.
Replies
sgarland • yesterday at 2:22 PM
IME, when performance issues become obvious, the devs are in growth mode and have no desire / time to revisit PK choice.
Integer PKs were seen as fine for years - decades, even - before the rise of UUIDs.
It's not really feasible to rekey your UUIDv4 keyed database to int64s after the fact, imo. Sure your new tables could be integer-keyed, but the bulk of your storage will be UUID (and UUIDv4, if that's what you started with) for a very long time