All Topics
Running Data Stores in Production
What goes wrong once a database is live: replication, failover, backups and concurrency, and how distributed databases fail in production.
Data Stores
Videos (2)
Podcasts (1)
Slide decks (1)
Infographics (1)
Sources (26)
- web page CAP Twelve Years Later: How the "Rules" Have Changed - InfoQ
- web page Consistency
- web page Evolutionary Database Design
- web page Google SRE - Cascading Failures: Reducing System Outage
- web page Google SRE - Data Integrity: Principles and Best Practices
- web page Google SRE: Load Balancing with Client Side Throttling
- web page How to do distributed locking — Martin Kleppmann's blog
- web page Jepsen: PostgreSQL 12.3
- web page Leader Election in Distributed Systems | AWS Builder Center
- web page Linearizability
- web page Parallel Change
- web page PgBouncer command-line usage
- web page Please stop calling databases CP or AP — Martin Kleppmann's blog
- web page PostgreSQL: Documentation: 18: 13.3. Explicit Locking
- web page PostgreSQL: Documentation: 18: 25.3. Continuous Archiving and Point-in-Time Recovery (PITR)
- web page PostgreSQL: Documentation: 18: 26.2. Log-Shipping Standby Servers
- web page PostgreSQL: Documentation: 18: Chapter 25. Backup and Restore
- web page PostgreSQL: Documentation: 18: Chapter 26. High Availability, Load Balancing, and Replication
- web page PostgreSQL: Documentation: 18: F.32. pg_stat_statements — track statistics of SQL planning and execution
- web page Serializability
- web page Snapshot Isolation
- web page Timeouts, retries, and backoff with jitter | AWS Builder Center
- web page Using load shedding to avoid overload | AWS Builder Center
- pdf raft
- pdf spanner-osdi2012
- web page https://www.odbms.org/wp-content/uploads/2013/11/06131212.pdf