OtterJun 30, 2024

8 versions of UUID and when to use them

https://lemmy.ca/post/24110505

8 versions of UUID and when to use them - Lemmy.ca

Show threadZikejiJun 30, 2024
Reject UUID embrace ULID.
Show threadπ™²πš‘πšŠπš’πš›πš–πšŠπš— π™ΌπšŽπš˜πš 
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.
Jun 30, 2024 at 7:55amWeb
Show threadshotgun_crabJun 30, 2024
I’ll be borrowing that little trick
Show threadπ™²πš‘πšŠπš’πš›πš–πšŠπš— π™ΌπšŽπš˜πš Jun 30, 2024

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!

GitHub - TheArchitectDev/Architect.Identities: Reliable unique ID generation for distributed applications.

Reliable unique ID generation for distributed applications. - TheArchitectDev/Architect.Identities

GitHub
Show threadRonSijmJul 2, 2024

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

GitHub - richardtallent/RT.Comb: Creating sequential GUIDs in C# for MSSQL or PostgreSql

Creating sequential GUIDs in C# for MSSQL or PostgreSql - richardtallent/RT.Comb

GitHub
Show threadπ™²πš‘πšŠπš’πš›πš–πšŠπš— π™ΌπšŽπš˜πš Jul 2, 2024

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

GitHub - TheArchitectDev/Architect.Identities: Reliable unique ID generation for distributed applications.

Reliable unique ID generation for distributed applications. - TheArchitectDev/Architect.Identities

GitHub