Why sortable IDs are useful
Many systems need unique identifiers for records, jobs, invoices, logs, or events. Fully random IDs are common, but timestamp-aware IDs can be easier to sort, debug, and store efficiently.
When to consider them
- Event streams where creation order matters.
- Database records where index locality helps.
- Logs or temporary references that benefit from readable ordering.
- Distributed systems that should avoid central ID counters.
Data handling and design limits
Timestamp-based identifiers can reveal approximate creation time. If that is sensitive, consider whether random identifiers are safer. Also avoid using public IDs as the only access control check.
FAQ
Are sortable IDs secure by default?
No. They are identifiers, not permissions. Authorization must still be enforced separately.
Can I use them in URLs?
Yes, but treat public URLs carefully and avoid exposing records that should be private.