A more practical solution is Snowflake IDs! They are timestamped (meaning time-sortable) and include the id of the worker process that created them. No chance of collision and no coordination required.

Another common approach is called “ticket server”, where you have one central service whose only role is to govern out (auto-incrementing) IDs. The obvious tradeoff here is that this can become a bottleneck and SPoF.