> You have a single DB running on a single machine. But you also care this much about write performance that you need sequential ids. How much longer is that si

> You have a single DB running on a single machine. But you also care this much about write performance that you need sequential ids. How much longer is that single DB going to work for you, if write performance has become an issue? Potentially a long time. Anecdotal: I helped a PG user in ~2012 (+- 2 years) to move to some sequential-ish uuid-like thing because they were facing outages, and as of last year they were still using a single instance for that service. And they grew by a lot. > Because soon you might need to shard, which you will lose sequential ids and benefit of spatial locality right? You don't need (not even want) perfect spatial locality. It's ok as long as it's not uniformly random.