✳flâneur — a map of the web's best reading
The Problem with Using a UUID Primary Key in MySQL — PlanetScale
planetscale.com · 1,789 words · saved by 1 readers
Understand the different versions of UUIDs and why using them as a primary key in MySQL can hurt database performance.
The Problem with Using a UUID Primary Key in MySQL Brian Morrison II | March 19, 2024 Universally Unique Identifiers, also known as UUIDs, are designed to allow developers to generate unique IDs in a way that guarantees uniqueness without knowledge of other systems. These are especially useful in a distributed architecture, where you have a number of systems and databases responsible for creating records. You might think that using UUIDs as a primary key in a database is a great idea, but when used incorrectly, they can drastically hurt database performance. In this article, you'll learn about
Explore this link on the map →related reading
- An in-depth look at Database Indexingfreecodecamp.org
- Build Your Own Databasenan.fyi
- Primary Key and Secondary Indexes in DynamoDB | by Mahima Manik | Mediummedium.com
- Designing APIs for humans: Object IDs - DEV Communitydev.to
- Things to keep in mind while picking a partition key in DynamoDB | by Ekta Garg | Mediummedium.com
- On Idempotency Keys - Gunnar Morlingmorling.dev
- Databases in 2024: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- Using Snowflakes for database IDs | Matteo Contrinimatteosonoio.it
- Moving away from UUIDs – Neil Maddenneilmadden.blog
- Database Fundamentalstontinton.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- A More Human Approach To Databasesccorcos.github.io