uuid7
ulid
uuid7 | ulid | |
---|---|---|
3 | 4 | |
68 | 644 | |
- | - | |
0.0 | 0.0 | |
4 months ago | about 1 year ago | |
Python | Python | |
MIT License | Apache License 2.0 |
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)
ulid
-
Plan B for UUIDs: double AES-128
I really like ULID for this problem (e.g: https://github.com/ahawker/ulid)
- same number of bytes as UUID
- start with a date, so has great locality. Plus you get extra information in the uid that you can extract.
- can be created from an existing date or uuid, and exported to a uuid, so there is a migration path
-
New UUID Formats from IETF
As the author of a popular ULID implementation in python[1], the spec has no stewardship anymore. The specification repo[2] has plenty of open issues and no real guidance or communication beyond language implementation authors discussing corner cases. The monotonic functionality is ambiguous (at best) and is implemented differently per-languages [3].
Functionality, UUIDv7 might be the _same_ but the hope would be for a more rigid specification for interoperability.
[1]: https://github.com/ahawker/ulid
[2]: https://github.com/ulid/spec
[3]: https://github.com/ulid/spec/issues/11
-
Sortable Collision-Free UUIDs
Looks similar to ULID[0] (I am the author of a popular python implementation[1]).
It appears to have a similar constraint that two ID's generated within the same timestamp (ms, ns) have no strong guarantee of ordering. That might not be a deal breaker depending on your use case but something to consider.
* https://github.com/ulid/spec
* https://github.com/ahawker/ulid
- Usando ULIDs para criar ordem em dados não ordenados
What are some alternatives?
uuid7-csharp - UUIDv7 for C#. Time-ordered UUIDs with up to 50ns resolution and 48 bits of randomness.
ksuid - K-Sortable Globally Unique IDs
python-ulid - ULID implementation for Python
Hashids.java - Hashids algorithm v1.0.0 implementation in Java
uuid - Generate RFC-compliant UUIDs in JavaScript
uuid6-ietf-draft - Next Generation UUID Formats
UUID - :snowflake: A PHP library for generating universally unique identifiers (UUIDs).
dart-uuid - Generate RFC4122(v1,v4,v5,v6,v7,v8) UUIDs
EXREX - Irregular methods on regular expressions
tiny_id - Rust library for generating non-sequential, tightly-packed short IDs.
xeger - Library to generate random strings from regular expressions.