Applying Continuous Delivery to Database Schema
summary
Claim: applying Continuous Delivery to database schema cuts deployment risk and speeds releases by putting schema changes through automated pipelines. Uses: versioned schema as code (Fauna FSL), Git-backed pipelines across dev/pre-prod/prod, a CLI to push endpoints and load sample data, automated tests and canary checks, and zero-downtime migrations with transactional apply and rollbacks. Example: Fauna runs a pipeline that applies schema changes to three environments (used for backup/restore) and reports successful, production-safe deployments. CLI endpoints
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:30Agenda
- 4:42What is Continuous Delivery
- 6:24Why would people not do this
- 9:05Requirements
- 11:09Validation
- 12:37Implementing Continuous Delivery
- 18:09Wrap Up
- 20:45Outro
related talks
45mEnabling Continuous Delivery with Database Practices
11mLightning Talk: Continuous Delivery…except for Database Changes
46mDatabase DevOps - It is Possible!
31mDevOps Practices for the Database Team
31mHelp! My Database Is The Bottleneck
30mExpand Contract Pattern for Continuous Delivery of Databases
01h 00mContinuous Integration and Delivery for Databases
59mNavigating the Challenges of CI /CD for Relational Database Schema Changes