Programming

17304 readers

56 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

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 [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

123

8 versions of UUID and when to use them (www.ntietz.com)

submitted 4 months ago by [email protected] to c/programming

29 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Zikeji 11 points 4 months ago (8 children)

Reject UUID embrace ULID.

[–] ChairmanMeow 12 points 4 months ago (4 children)

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.

[–] RonSijm 1 points 4 months ago (1 children)

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

[–] ChairmanMeow 2 points 4 months ago

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

load more comments (2 replies)

load more comments (5 replies)