You can have both asynchrony and sequence by encoding thread ID in the UUID too, and make the sequence a thread local state.

MongoDB uses a similar approach. https://www.mongodb.com/docs/manual/reference/method/ObjectI...

Then, just use thread ID and integer sequence pairs instead of trying to stuff them into an arbitrary binary format.

Thread IDs get repeated across reboots. Integer sequence may also repeat in a distributed scenario, unless you want a massive bottleneck. You do need other stuff (timestamps, random number, etc.).

Yes, but that’s what parent proposed? :shrug: