js-id
ksuid
Our great sponsors
js-id | ksuid | |
---|---|---|
3 | 38 | |
10 | 4,679 | |
- | 2.2% | |
5.9 | 3.1 | |
8 months ago | 7 months ago | |
TypeScript | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
js-id
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
We have a uuidv7 implementation that we've been using with rocksdb for over a year https://github.com/matrixai/js-id
-
Plan B for UUIDs: double AES-128
We evaluated ULID but we wanted something that is future proof for our decentralised secret sharing system. So we implemented UUIDv7 in TypeScript called `IdSortable` https://github.com/MatrixAI/js-id
It allows strict monotonic IDs when you provide it the previously generated ID. The resulting data structure is a Uint8Array making it easy to put into binary structures. Can also be used as a key inside any POJO record.
-
Lesser Known PostgreSQL Features
I had reviewed existing UUIDv7 implementations and many were incorrect or had subtle timing bugs.
We ended up implementing UUIDv7 in our ID generation library https://github.com/MatrixAI/js-id. And we have a number of tests ensuring that it is truly monotonic even across process restarts.
See IdSortable.
ksuid
- What happens after 100 years?
-
Zero Downtime Postgres Upgrades
OP here - we avoid sequences in all but one part of our application due to a dependency. We use [KSUIDs][1] and UUID v4 in various places. This one "gotcha" applies to any sequence, so it's worth calling out as general advice when running a migration like this.
[1]: https://segment.com/blog/a-brief-history-of-the-uuid/
-
Bye Sequence, Hello UUIDv7
UUID v4 isn't large enough to prevent collisions, that is why segment.io created https://github.com/segmentio/ksuid which is 160bit vs the 128bit of a UUIDv4.
- You Don't Need UUID
- A Brief History of the UUID
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
Assuming you don't need to use UUIDv7 (or any UUID's) then https://github.com/segmentio/ksuid provides a much bigger keyspace. You could just append a string prefix if you wanted to namespace, but the chance of collisions of a KSUID is many times smaller than a UUID of any version.
-
Unexpected downsides of UUID keys in PostgreSQL
KSUID's are have temporal-lexicographical order plus 128 bits of entropy, which is more than UUIDv4.
https://github.com/segmentio/ksuid
-
UUIDs are so much better than autoincrementing ids and it's not even close
That's why you use ksuid (https://segment.com/blog/a-brief-history-of-the-uuid/) or, if you're willing to go with a draft spec you could go with the new UUID formats https://www.ietf.org/archive/id/draft-ietf-uuidrev-rfc4122bi...
-
What Happened to UUIDv2?
Interesting in more history of UUIDs? Twilio Segment's blog has an amazing history lesson about how they came to be.
-
Which UUID package do you use? and why?
I use the ksuid from segment. https://github.com/segmentio/ksuid
What are some alternatives?
typeid - Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
ulid - Universally Unique Lexicographically Sortable Identifier (ULID) in Python 3
typeid-go - Go implementation of TypeIDs: type-safe, K-sortable, and globally unique identifiers inspired by Stripe IDs
pg-ulid - ULID Functions for PostgreSQL
tbls - tbls is a CI-Friendly tool for document a database, written in Go.
nanoid - A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript
resource-id - Developer-friendly k-sortable IDs
ulid-mssql - Implementation of ULID generator For Microsoft SQL Server
postgres-elasticsearch-fdw - Postgres to Elastic Search Foreign Data Wrapper
python-ksuid - A pure-Python KSUID implementation
afid
uuid7 - UUID version 7, which are time-sortable (following the Peabody RFC4122 draft)