|
You are here |
timilearning.com | ||
| | | | |
www.adamconrad.dev
|
|
| | | | | Ch 3 of my book club review of Designing Data-Intensive Applications by Martin Kleppmann. | |
| | | | |
sookocheff.com
|
|
| | | | | A central tenet of databases is that any committed data survives a crash or a failure. Write-ahead logging is a fundamental primitive that ensures all changes to data are first written safely to stable storage before being applied. Coupling that with some careful use of sequence numbers and we can guarantee that changes made to a database can survive system crashes. Motivation Let's start with a simple transaction T1 that reads object A, and updates the value for A with a write. To simplify matters, A is... | |
| | | | |
ordep.dev
|
|
| | | | | [AI summary] A transcript of a talk comparing log-structured storage engines like LSM-Trees with traditional B-Trees, discussing their architectures, performance trade-offs, and underlying data structures. | |
| | | | |
www.themindiseverything.eu
|
|
| | | ( TL;DR version ) Issues in cloud-based deployments totally dominated the database topics on both, Fosdem and p2d2 conferences. Whether it i... | ||