Moving Away from UUIDs

• ksuid

  39 4,884 3.1 Go

  K-Sortable Globally Unique IDs

  

  There are KSUIDs that aim to satisfy this

  A go ref impl: https://github.com/segmentio/ksuid

• InfluxDB

  www.influxdata.com featured

  Purpose built for real-time analytics at any scale. InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.

  

• nanoid

  85 24,266 8.3 JavaScript

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

  I really like https://github.com/ai/nanoid which is available for a wide range of programming languages. It creates short, random, and URL-safe IDs.

• spec

  63 9,556 0.0

  The canonical spec for ulid

  

  These days ULID (https://github.com/ulid/spec, or any of the variants), or most recently the new UUID versions (https://www.ietf.org/archive/id/draft-peabody-dispatch-new-u...) give you creation-order sorting.

• short-uuid

  2 452 4.7 JavaScript

  Translate standard UUIDs into shorter formats and back.

  > The dash-separated hexadecimal format takes 36 characters to represent 16 bytes of data.

  You can use a different formatting. I would suggest looking at https://github.com/oculus42/short-uuid Of course if you just want a random ID, then you might not need a UUID. But UUIDs have the advantage that there are different versions and you can distinguish them; e.g. you might want a unique ID that gives you some debugging information (where/when was it created), so you use v1 and later you can decide to switch to v4 if decide you want the IDs to carry no information.

  Indepedent of how you generate the ID, I think the base-57 encoding that shortUUIDs use is quite good when the IDs are user facing. Not using O,0,l,1,I in the alphabet makes IDs more readable.

Suggest a related project