Instagram use a custom scheme (instagram-engineering.com/sharding...) as they need time-sortable unique IDs across multiple DB servers (shards). They implemented it in PL/SQL, composing an ID from the current time, the shard ID, and an auto-increment, giving 1024 IDs per shard per millisecond. Pretty cool, check out the link.
It's pretty cool indeed! Thank you! In our case I think it should be abstracted from the DB but that's just an implementation detail
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.