Help! My Database Is The Bottleneck
summary
Argues the database stops shipping when schema changes are ad hoc and ops stay siloed and offers concrete remedies: adopt schema versioning, build automated migrations that run in CI, and add unit and integration tests against real data snapshots. Describes a small pipeline built to run migrations, test rollbacks, and measure latency before and after, showing a measurable drop in deploy time and fewer emergency fixes. Notes special constraints — live migrations, backups, and coordination with change windows.
AI-written summary · about
chapters (6)
- 0:00Welcome and problem intro
- 5:45Symptoms of bottleneck
- 12:46Basic DB diagnostic tools
- 18:58Estrategias comunes para optimizar consultas
- 25:18Casos prácticos y ejemplos de mejora
- 30:50Conclusiones y preguntas frecuentes
related talks
45mEnabling Continuous Delivery with Database Practices
33mDatabase Schema Migrations with Zero Downtime
31mDevOps Practices for the Database Team
37mDatabase Schema Migrations with Zero Downtime
11mLightning Talk: Continuous Delivery…except for Database Changes
46mDatabase DevOps - It is Possible!
05mMaking Database Changes a Tier one Artifact
27mDevOps and the Database Bottleneck