Bridging the Gap: The Vital Role of DBAs while contributing to the DevOps Culture
summary
Experienced DBAs provide concrete fixes: they catch a deployed update that forgot WHERE clause and caused table-wide locks, add a missing index to stop full-table scans that turned 4s queries into milliseconds, and rewrite a 12-table ORM join into paginated reads to avoid massive locking and cut runtime to seconds. They manage MySQL replicas, Aurora and Postgres failovers, and warn that replication lag and poor backup restores (GitLab 2017 style) cause partial data loss. Practical rule: untested backups are not backups.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 1:00Who are DBAs and their role
- 4:56Typical DBA challenges and rules
- 7:47DevOps and team collaboration
- 12:49Funny perspectives on DBAs and developers
- 13:54Outages vs service degradation
- 14:37Real-world database incident stories
- 20:57Database design and scalability
- 23:26Backup and recovery best practices
- 27:44Horror stories and lessons learned
- 33:23Dependencies and single points of failure
- 35:53Testing and meaningful alerts
- 38:03Backup procedures and recovery objectives
- 40:13Q&A session
related talks
05mCommon mistakes of DBAs
47mAgile DBA - How to Be a DBA in the Midst of the Agile Revolution?
33mBringing DevOps To The Database
36mUnlocking the Benefits of Database DevOps and Automation
30mWorking with DBAs in a DevOps World
23mBridging the DevOps Gap in Modern Data Teams
50mTransforming Your DBA Team Into a DBRE/SRE One!
44mConfessions of a DBA: worst and best things I've done in production