Otter8 versions of UUID and when to use them
ZikejiReject UUID embrace ULID.
π²πππππππ πΌπππ 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.
RonSijmbase63? 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: github.com/TheArchitectDev/Architect.Identities
