uuid7
ksuid
| uuid7 | ksuid | |
|---|---|---|
| 3 | 38 | |
| 68 | 4,691 | |
| - | 1.0% | |
| 0.0 | 3.1 | |
| 4 months ago | 7 months ago | |
| Python | Go | |
| MIT License | 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.
uuid7
-
Sequential UUID in snowflake
Snowflake does not support UUID 7. What you could do is import UUID7 Python module and implement a Python UDF.
- New UUID Formats from IETF
-
Understanding UUIDs, ULIDs and String Representations
To summarise the differences:
* UUIDv6 - sortable, with a layout matching UUIDv1 for backward compatibility, except the time chunks have been reordered so the uuid sorts chronologically
* UUIDv7 - sortable, based on nanoseconds since the Unix epoch. Simpler layout than UUIDv6 and more flexibility about the number of bits allocated to the time part versus sequence and randomness. The nice aspect here is the uuids sort chronologically even when created by systems using different numbers of time bits.
* UUIDv8 - more flexibility for layout. Should only be used if UUIDv6/7 aren't suitable. Which of course makes them specific to that one application which knows how to encode/decode them.
UUIDv7 is thus the better choice in general.
(I recently wrote Python and C# implementations - https://github.com/stevesimmons/uuid7 and https://github.com/stevesimmons/uuid7-csharp)
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?
uuid7-csharp - UUIDv7 for C#. Time-ordered UUIDs with up to 50ns resolution and 48 bits of randomness.
ulid - Universally Unique Lexicographically Sortable Identifier (ULID) in Python 3
Hashids.java - Hashids algorithm v1.0.0 implementation in Java
pg-ulid - ULID Functions for PostgreSQL
uuid6-ietf-draft - Next Generation UUID Formats
nanoid - A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript
dart-uuid - Generate RFC4122(v1,v4,v5,v6,v7,v8) UUIDs
ulid-mssql - Implementation of ULID generator For Microsoft SQL Server
python-ksuid - A pure-Python KSUID implementation
tiny_id - Rust library for generating non-sequential, tightly-packed short IDs.
cuid - Collision-resistant ids optimized for horizontal scaling and performance.