123
8 versions of UUID and when to use them
(www.ntietz.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 30 Jun 2024
123 points (98.4% liked)
Programming
17314 readers
78 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
At the company I work at we use UUIDv7 but base63 encoded I believe. This gives you fairly short ids (16 chars iirc, it includes lowercase letters) that are also sortable.
base63? I'd guess you'd mean base64?
Anyways, doesn't that fuck with performance?
I'm using this in production: RT.Comb - That still generates GUIDs, but generates them sequential over time. Gives you both the benefits of sequential ids, and also the benefits of sequential keys. I haven't had any issues or collisions with that
It's Base62 actually, misremembered that. It's to avoid some special characters iirc. And no, performance is fine.
We're using this: https://github.com/TheArchitectDev/Architect.Identities
I'll be borrowing that little trick
https://github.com/TheArchitectDev/Architect.Identities
Here's the package one of our former developers created. It has some advantages and some drawbacks, but overall it's been quite a treat to work with!