ulid
typeid-go
Our great sponsors
| ulid | typeid-go | |
|---|---|---|
| 11 | 2 | |
| 4,108 | 101 | |
| 2.0% | - | |
| 4.5 | 7.0 | |
| 14 days ago | 4 days ago | |
| Go | Go | |
| Apache License 2.0 | 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.
ulid
-
Nanosecond timestamp collisions are common
Our Go ULID package has millisecond precision + monotonic random bytes for disambiguation while preserving ordering within the same millisecond. https://github.com/oklog/ulid
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
There is no "tests".
There is just a single test. Which only tests the decoding of a single known value. No encoding test.
Go has infrastructure for benchmarking and fuzzing. Use it!
Also, you took code from https://github.com/oklog/ulid/blob/main/ulid.go which has "Copyright 2016 The Oklog Authors" but this is not mentionned in your base32.go.
-
cmackenzie1/go-uuid: library for generating version 4 (random) and version 7 (time-ordered) UUIDs
maybe because of dependencies: https://github.com/oklog/ulid/blob/main/go.mod ??
- The most helpful Go Packages
-
UUIDs Are Bad for Database Index Performance, enter UUID7!
Universally Unique Lexicographically Sortable Identifier
-
Is it bad to use short (20 chars) random strings as primary keys?
I'm not concerned too much about the performance or the storage size at this stage. I've checked ulids before posting (more specifically https://github.com/oklog/ulid) but the only difference than a random string (especially if you use them with math.rand) is the timestamp prefix which makes them sortable, but I don't need that (users could use the internal SQLite rowid if they needed to sort by a primary key).
- UUIDs Are Popular, but Bad for Performance
-
Golang Base Project - A simple web app with user authentication
why are you using https://github.com/oklog/ulid to generate a cookie secret?
-
What are your favorite packages to use?
oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).
-
Keyset pagination using UUID v4 mongodb go
If you just want to roll with an off-the-shelf library, you can use ULID. There are tons of custom made *flake alternatives. If ULID doesn't fit your purposes, look for others.
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!
What are some alternatives?
nanoid - A tiny and fast Go unique string generator
typeid - Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
xid - xid is a globally unique id generator thought for the web
resource-id - Developer-friendly k-sortable IDs
gouid - Fast, dependable universally unique ids
launchpad - From Code to Kubernetes in One Step.
sno - Compact, sortable and fast unique IDs with embedded metadata.
brain - Swyx's second brain!
Monoton - Highly scalable, single/multi node, sortable, predictable and incremental unique id generator with zero allocation magic on the sequential generation
saltpack - a modern crypto messaging format
goflake - A highly scalable and serverless unique ID generator for use in distributed systems. Written in GoLang. Inspired by Twitters Snowflake.
spec - The canonical spec for ulid