Data EngineeringAdvanced9 submodules

Database CI/CD and Schema Evolution

Version, validate, package, migrate, and recover relational database schema changes using SQL scripts, DACPAC, Flyway, or Liquibase in a controlled delivery pipeline.

How this module works

From concept to production evidence

Treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Learning outcomes

Design database CI/CD
Version SQL and schemas
Compare DACPAC with Flyway and Liquibase
Plan backward-compatible migrations
Secure deployments and test rollback or recovery

Flow diagram

Database CI/CD and Schema Evolution end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

01
Change schema codeDatabase CI/CD and Schema Evolution stage 1: change schema code with an auditable result before the next stage begins.
02
Build and validateDatabase CI/CD and Schema Evolution stage 2: build and validate with an auditable result before the next stage begins.
03
Package or order migrationDatabase CI/CD and Schema Evolution stage 3: package or order migration with an auditable result before the next stage begins.
04
Back up and approveDatabase CI/CD and Schema Evolution stage 4: back up and approve with an auditable result before the next stage begins.
05
Deploy with lockDatabase CI/CD and Schema Evolution stage 5: deploy with lock with an auditable result before the next stage begins.
06
Verify data and recover if neededDatabase CI/CD and Schema Evolution stage 6: verify data and recover if needed with an auditable result before the next stage begins.

Integrated hands-on lab

Deliver a backward-compatible schema change

Create versioned migration
Validate on disposable database
Publish artifact or migration bundle
Run expand and data backfill
Verify application compatibility and contract cleanup

Complete module contents

9 full submodule notes

Read in order

Database CI/CD

Database CI/CD preserves durable information with explicit ownership, consistency, access, lifecycle, replication, and recovery guarantees within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

SQL scripts

SQL scripts governs how a request is named, addressed, routed, filtered, transported, protected, and delivered to a healthy endpoint within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

Schema versioning

Schema versioning provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

DACPAC

DACPAC provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

Flyway

Flyway provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

Liquibase

Liquibase provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

Database migrations

Database migrations preserves durable information with explicit ownership, consistency, access, lifecycle, replication, and recovery guarantees within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

Rollback

Rollback restores a safe service state while preserving evidence and reducing the chance that mitigation introduces a second failure within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes

Secrets management

Secrets management controls which actor may perform which action on which resource, under which conditions, with evidence that can be reviewed later within Database CI/CD and Schema Evolution. It is not an isolated definition: its value appears when it supports treat schema as code, detect drift, test migrations against representative data, use expand-migrate-contract for compatibility, protect connection secrets, take recoverable backups, and prefer forward repair when rollback would lose data.

Open full notes