> If you're using UUIDs, there's probably a reason.
Not really; think of how many architectural decisions are made purely based on imaginary scaling problems, or what the latest blog said.
I would wager that if you polled 100 backend devs, very few of them could correctly articulate the pros and cons of a randomized primary key.
In both cases I'm melding highly disjointed data into a single schema. There are no large consecutive sets of records.
If you're using UUIDs, there's probably a reason. And that reason invalidates the justifications for not using them.