Skip to content
0:00 / 0:00

#hashids#guid#uuid

GUIDs and UUIDs are cool, but this is cooler

Nick Chapsas

429K subscribers • 62 videos on Hallway

YouTube
  • Recommended by 5 people: 5 in engineering communities.
  • Presented by Nick Chapsas
  • Linked in the descriptionullmark/hashids.net
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

183K views4 years ago5 recommendations

Databases and dataSoftware designDatabase internalsAPI designC# and .NET

Nick Chapsas explains how to use sequential IDs with HashIds to optimize database performance while keeping public identifiers unguessable.

Check out my courses and use code 100K for 20% off: dometrain.com Become a Patreon and get source code access: patreon.com/nickchapsas Hello everybody I'm Nick and in this video I will show you how you can use sequential ids as primary keys in your database without having to worry about security vurnabilities. This will allow you to have better potential database performance without having to worry about issues such as fragmentation if you use GUIDs or UUIDs are the primary key. Give HashIds a star on GitHub: github.com/ullmark/hashids.net Timestamps The problem - The solution - Library deep dive - Performance - Don't forget to comment, like and subscribe :) Social Media: Follow me on GitHub: bit.ly/ChapsasGitHub Follow me on Twitter: bit.ly/ChapsasTwitter Connect on LinkedIn: bit.ly/ChapsasLinkedIn Keep coding merch: keepcoding.shop #csharp #dotnet

Why it's here

5 people recommend this

What people say. Engineers recommend this video for understanding how to avoid GUID fragmentation in databases while keeping public IDs secure.

Moments people linked to

u/anachronisdevin r/dotnet • Recommends

On “Using HashIds with Dotnet”

I think this video by Nick Chapsas explains it quite well. You want the performance on the database which comes from serial IDs but the "unguessability" from hash-ids
4View on Reddit

u/bakedsnowmanin r/dotnet • Recommends

On “GUID looks ugly in front-end, what is your approach?”

HashIDs is a great way to make GUIDs a lot more manageable. The repo is here: https://github.com/ullmark/hashids.net Nick Chapsas has a good video going over it too: link to this video

u/BuriedStPatrickin r/dotnet • Recommends

On “Primary key Discussion: Using GUID vs Integers for Microservices”

…rtain advantages to GUIDs in your database depending on the technology used if you, for instance, need to index or page the results in a particular way. You could what YouTube does - generate a deterministic slug string based on the ID and expose this from your API. See this video for details on how to implement this using an open source package: link to this video However, it might be easier to just have an additional column for a "human readable ID" that's set based on some other parameters wherever the record's created or updated. For instance, you could have your application generate it based on a template string like "{customer}-{solution}-{name}" (or whatever properties your records have).…

u/subjective0in r/dotnet • Recommends

On “Primary key Discussion: Using GUID vs Integers for Microservices”

I think nick chapsas had a video on a library that can shorten guids and get the original guid from the short version. YouTube video

u/OpenedSaltin r/dotnet • Recommends

On “GUID looks ugly in front-end, what is your approach?”

You can check out this video: *link to this video