/explore
|
You are here 
|
dylanpaulus.com | ||
| | | | |
www.darrenhorrocks.co.uk
|
|
| | | | | One of the first schema decisions you face when designing a database table is: Should I use an INT or a UUID as the primary key? Most developers default to an auto-incrementing integer. It's simple, compact, and familiar. But UUIDs (a.k.a. GUIDs) are increasingly popular - and many of the old performance objections don't hold up with modern hardware. Let's break this down like developers, not DB theorists. | |
| | | | |
timilearning.com
|
|
| | | | | My notes from the second chapter of Martin Kleppmann's book: Designing Data Intensive Applications. | |
| | | | |
martinheinz.dev
|
|
| | | | | When working with databases, most of the time, all you need is SELECT, UPDATE (CRUD operations),... | |
| | | | |
johnjr.dev
|
|
| | | When we study transactions in relational databases, one of the first things we learn are the guarantees that a transaction must provide. ACID(Atomicity, Consistency, Isolation, Durability) are the properties that we desire. Here, I will discuss the Isolation level in more detail and show that atomicity alone is not enough when handling concurrency. One classic example of the importance of atomicity is moving money between accounts. So, imagine that we have two accounts and we would like to transfer the total amount from one account to another one. In a relational database, what we need to do is three steps: | ||
