typeid-go
ksuid
| typeid-go | ksuid | |
|---|---|---|
| 2 | 38 | |
| 105 | 4,702 | |
| 15.2% | 1.2% | |
| 7.0 | 3.1 | |
| 20 days ago | 7 months ago | |
| Go | 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.
typeid-go
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
We've now implemented pretty thorough testing: https://github.com/jetpack-io/typeid-go/blob/main/typeid_tes...
Thanks for the feedback!
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
ulid - Universally Unique Lexicographically Sortable Identifier (ULID) in Go
pg-ulid - ULID Functions for PostgreSQL
resource-id - Developer-friendly k-sortable IDs
nanoid - A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript
launchpad - From Code to Kubernetes in One Step.
ulid-mssql - Implementation of ULID generator For Microsoft SQL Server
brain - Swyx's second brain!
python-ksuid - A pure-Python KSUID implementation
saltpack - a modern crypto messaging format
uuid7 - UUID version 7, which are time-sortable (following the Peabody RFC4122 draft)