Database Guardrails - New Age for Developers and Databases
summary
Argues that developers must own their databases by catching bad SQL before deploy, using OpenTelemetry to capture traces and database EXPLAIN plans to compare execution costs, and integrating those checks into CI/CD so issues surface in development not after load tests. Describes a working guardrail flow: collect telemetry, detect index regression (query used an index last week and stopped), alert with a suggested index change, and run automated remediation or rollback.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:49Evolution of database complexity
- 6:09Common database failure points
- 9:37ORM limitations and risks
- 11:23Testing gaps in database operations
- 13:07Need for database guardrails
- 16:22OpenTelemetry for observability
- 18:56Execution plans for query analysis
- 20:40Developer ownership of databases
- 21:20Conclusion and Q&A
related talks
54mDatabase Guardrails - new age for developers and databases
37mPlatform Engineers Must Change Developers and Databases - And Here Is How
48mMissing chapter in your CI playbook: database guardrails
21mAgents on GuardRails: Deterministic Safety for Database Operations
17mEmpowering Engineers With a Database DevOps Strategy
36mUnlocking the Benefits of Database DevOps and Automation
20mManaging the Challenge of Monitoring Growing, Multi-platform Database Estates
44mBridging the Gap: The Vital Role of DBAs while contributing to the DevOps Culture