What does HackerNews think of typeid?

Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs

Language: Go

You Don't Need UUID | Sep 2023

IMO, a good middleground is using schemes like TypeID[0], ulid[1], or KSUID[2] that provides a more compact and readable (base32) representation and provides better database locality (K-sortable).

[0] https://github.com/jetpack-io/typeid [1] https://github.com/ulid/spec [2] https://github.com/segmentio/ksuid

You Don't Need UUID | Sep 2023

Expand Context ↕

They use a type safe extension of UUIDv7 Here is a go implementation and explanation: https://github.com/jetpack-io/typeid

Unexpected downsides of UUID keys in PostgreSQL | Jun 2023

The stated downsides come from poor data locality when using mostly random UUIDs; but you can keep most of the benefits of a globally unique identifier, and retain locality, by using UUIDv7.

At jetpack.io we've been doing exactly that via TypeIDs: https://github.com/jetpack-io/typeid and there's a PostgresSQL implementation available. TypeIDs are UUIDv7 with additional type information, so you also get type-safety in your IDs.