EIDs (Encoded IDs)

https://docs.crunchybridge.com/api-concepts/eid/

by brandur • 4 years ago

14 7 4 years ago

docs.crunchybridge.com

winslett• 4 years ago

Love the “easy to select for copy and paste” as a usability requirement.

Not gonna lie, UUIDs are awful and I agree with that being a requirement. My personal favorite is actually Amazon's ID system. The fact that at a glance I know what type/class of resource something is phenomenal.

Looking at you Azure. You GUID dumpster-fire of an API.

atonse• 4 years ago

I also like Stripe's prefixes. like sk_ or card_ etc.

Removes any ambiguity.

Scaevolus• 4 years ago

Note that the standard base32 rfc encoding does not sort the same as the underlying data, but the hex encoding does! (base32.HexEncoding).

Reddit uses base36 for similar purposes.

snthpy3• 4 years ago

Why is this? Because of the optional padding?

snthpy3• 4 years ago

So kinda like ULIDs (except when not using the time based generating algorithm) and using standard-base32 instead of Crockford's base 32?

snthpy3• 4 years ago

I'd love to use this instead of UUIDs. Is there an easy to install PostgreSQL extension?

EIDs (Encoded IDs)

Related Stories