So Clubhouse violated one fundamental concept of API architecture. That not to expose numerically incrementing unique identifiers.

• pg_random_id

  1 5 0.0 Ruby

  Discontinued Provides pseudo-random IDs in Postgresql databases

  

Or, my favorite - https://github.com/conjurinc/pg_random_id - map integer keys to a different, apparently random id using a Feistel cypher

• ksuid

  38 4,682 3.1 Go

  K-Sortable Globally Unique IDs

  

give this one a read. https://segment.com/blog/a-brief-history-of-the-uuid/

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• nanoid

  83 23,187 8.3 JavaScript

  A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript

• hscuid

  1 10 0.0 Haskell

  Collision-resistant IDs for horizontal scaling

• spec

  62 8,648 0.0

  The canonical spec for ulid

  

In the article it's mentioned that there is a better way than UUIDv4 or using machine identifiers. I expected ULID and got something that's not even UUID binary compatible. https://github.com/ulid/spec

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project