Otter@lemmy.ca to Programming@programming.devEnglish · 4 months ago8 versions of UUID and when to use themwww.ntietz.comexternal-linkmessage-square29fedilinkarrow-up1125arrow-down12
arrow-up1123arrow-down1external-link8 versions of UUID and when to use themwww.ntietz.comOtter@lemmy.ca to Programming@programming.devEnglish · 4 months agomessage-square29fedilink
minus-squareRonSijm@programming.devlinkfedilinkarrow-up1·4 months agobase63? 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
minus-square𝙲𝚑𝚊𝚒𝚛𝚖𝚊𝚗 𝙼𝚎𝚘𝚠@programming.devlinkfedilinkarrow-up2·4 months agoIt’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
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