~/talk

DevOps Practices for the Database Team

Talkat DevOpsDays Chicago 2017 · 2017-09-12..09-13· [databases]
slides:none on file

Argues for putting all database artifacts in version control and running schema changes through CI/CD with migration frameworks like liquibase, flyway, dbdeploy so database changes package with the app. Shows automated sandbox provisioning using docker images for DB sandboxes, scripts that generate grants and boilerplate, a tablespace-mapping pipeline, and expand-and-contract refactoring to keep old and new schemas working. Recommends rolling forward rather than complex rollbacks and deploying frequently (example: regular weekly releases) to reduce risk.

AI-written summary · about

  1. 0:00Start
  2. 1:32WHAT DOES DEVOPS MEAN FOR THE DATABASE TEAM?
  3. 2:43Put all database artifacts in version control Everyone should be able to see all the artifacts of the system.
  4. 4:05Generate as much database boiler plate code as possible. Put the code generation in a pipeline
  5. 8:52Write database migration during development time. Pairing with the DBA's is important to understand production size and data complexity
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.