Platform Engineers Must Change Developers and Databases - And Here Is How
summary
Platform engineers push detailed database guardrails that project developer work onto production by capturing OpenTelemetry from local, CI and prod and project queries onto production to generate execution plans and actionable fixes. Examples: a single join query returns 300,000 rows and runs 25 seconds, refactoring to smaller queries speeds it up; refactoring with a CTE changes runtime from 8s to 13s. Load tests take hours and schema migrations can take minutes hours or even days so early projection prevents costly late failures.
AI-written summary · about
chapters (12)
- 0:00Platform engineering intro
- 1:54Databases missing in DevOps
- 4:23Conway’s law and silos
- 8:19Shift DB issues left
- 11:09DB performance testing blind spots
- 14:44Query performance examples
- 20:20Introducing database guardrails for developers
- 23:10Observability across dev/prod
- 26:25Auto code reviews for queries
- 28:35Changing processes to empower developers
- 31:27Summary and call to action
- 31:58Q&A
related talks
50mAdam Furmanek: You Must Test Your Databases And Here Is How
54mDatabase Guardrails - new age for developers and databases
17mEmpowering Engineers With a Database DevOps Strategy
22mDatabase Guardrails - New Age for Developers and Databases
48mMissing chapter in your CI playbook: database guardrails
23mShift-Left: A DevOps and Database Story- 23mShift-Left: A DevOps and Database Story
31mHelp! My Database Is The Bottleneck