Unexpected downsides of UUID keys in PostgreSQL

1. ksuid

   1 39 5,110 3.1 Go

   K-Sortable Globally Unique IDs

   

   If size isn't an issue it seems so. I know of one implementation that uses wall clock to get a "close enough" sorting https://github.com/segmentio/ksuid

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. deterministic-guid-generator

   2 1 38 4.2 C#

   Create a deterministic GUID based on namespace Guid, a string and an optional version.

   

   Tbh. I love UUID's.

   The next thing i prefer is Deterministic UUID's,

   eg. DeterministicGuid.Create(tenantNamespace, "my-tenant-name");

   Note: https://github.com/Informatievlaanderen/deterministic-guid-g... for dotnet.

4. deterministic-guid-g

   3 1 - -

   Tbh. I love UUID's.

   The next thing i prefer is Deterministic UUID's,

   eg. DeterministicGuid.Create(tenantNamespace, "my-tenant-name");

   Note: https://github.com/Informatievlaanderen/deterministic-guid-g... for dotnet.

5. flow

   4 10 770 9.9 C++

   🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊 (by estuary)

   

   We use a macaddr8 that embeds a wall-clock timestamp (so they're ascending order, achieving data locality) with some additional randomness. It's worked really well for us:

   https://github.com/estuary/flow/blob/master/supabase/migrati...

   we use macaddr8 instead of bigint, because it has a postgres serialization / JSON encoding which lossless-ly round-trips with browsers and it works well with PostgREST. The same CANNOT be said for bigint, which is a huge footgun.

6. typeid

   5 22 3,355 7.4 Go

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

   

   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.

7. Stream

   getstream.io featured

   Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

   

Suggest a related project