What database were you using? For example with SQL server, by default it clusters data on disk by primary key. Random (non-sequential) PKs like uuidv4 require random cluster shuffling to insert a row “in the middle” of a cluster, increasing io load and causing performance issues.

Postgres on the other hand doesn’t do clustered indexing on the PK… if I recall correctly.

▲

rvitorper a day ago | parent | next [-]

Postgres. It was also a single instance, which made it significantly easier. But nice to know that this is an issue on SQL Server

▲

masklinn a day ago | parent [-]

Postgres is not immune to uuid issues, just less sensitive, uuidv4 still does not play well with btree indexes, bloating them and impacting their performance.

▲

ahoka a day ago | parent [-]

Do you also require your users to register in the alphabetical order of their names?

	▲	rkomorn a day ago \| parent \| next [-]
		New viral marketing idea just dropped: registration open to b-names only! Get in now before you lose your chance forever to the c-names!
	▲	20 hours ago \| parent \| prev [-]
		[deleted]

▲

ahoka a day ago | parent | prev [-]

Then cluster it differently? The whole problem uuidv7 in databases solves is a non-issue in most cases.