Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> the random nature of standard non-time-ordered UUIDs (such as v4) can create database performance problems when used as primary keys. This problem is often referred to as poor database index locality.

Couldn't that be solved with incremented serial numbers, rather than leaking time data?



Yes. But I think part of the design requirements is minimizing coordination required among distributed nodes.

This solution attempts to solve the sort-ability issue of current uuids by moving the timestamp to the most significant bits.


Incremented serial numbers can leak things like eg. volume of sales in your shop.


So increasing serial numbers with random gaps?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: