Understanding UUIDs, ULIDs and string representations
1–10 of 104 posts
Re: Understanding UUIDs, ULIDs and string representations
#2Author here, self-posted. AMA.
Re: Understanding UUIDs, ULIDs and string representations
#3Why not CUID?
Re: Understanding UUIDs, ULIDs and string representations
#4Why not CUID?
Haven’t looked into it, will check it out.
Re: Understanding UUIDs, ULIDs and string representations
#5First time hearing about ULIDs. The locality is interesting, but they leak information about when they were generated down to the millisecond, which could lead to problems if combined with other issues. I'd be wary of using them client-side.
Re: Understanding UUIDs, ULIDs and string representations
#6For anyone else wondering: ULID = Unique Lexicographically IDentifiers
Re: Understanding UUIDs, ULIDs and string representations
#7Author here, self-posted. AMA.
I just want to say that I really enjoyed reading this article. It's among the clearest, most accessible writing about a technical subject that I've encountered in a while.
Re: Understanding UUIDs, ULIDs and string representations
#8Why not CUID?
Snowflake ID[1] is another system related to those in the article. It uses 64 bits only, and has good sharding support, so can be more useful in some contexts. However, it naturally has worse independent random-collision chances than a 128 bit system.
[1] https://en.wikipedia.org/wiki/Snowflake_ID
Re: Understanding UUIDs, ULIDs and string representations
#9There's also a proposal for UUIDv6-8, lexicographically sortable variants.
https://datatracker.ietf.org/doc/html/draft-peabody-dispatch...
Re: Understanding UUIDs, ULIDs and string representations
#10Most people are familiar with time and random UUIDs but and I had sort of known about v5 UUIDs but recently used them to get consistent identifiers from an input value… super useful because you can do `uuidv5($namespace_uuid, data)` and get the same UUID everytime.