Beyond Alembic and Django Migrations
summary
Compares Alembic/Django migration limits with Atlas, a schema-as-code engine that auto-generates diffs from SQLAlchemy models plus layered SQL and actually handles materialized views support and stored objects instead of forcing manual DDL. Shows Atlas producing migrations, running schema tests (HCL format), linting migrations with warnings for destructive or lock-heavy ops, and CI/CD integrations (GitHub actions, Terraform provider, Kubernetes operator). Mentions a checkpoint squashing feature to speed large deploys and migration linter and CI checks that block risky PRs.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 4:59Limitations of ORM-native tools
- 12:22Introducing Atlas for advanced migrations
- 16:35CI/CD integration for migrations
- 23:12When to consider Atlas
- 24:16Q&A session
related talks
56mSane schema migrations with Alembic and Postgres
33mAvoid Toll Roads: Deploying Declarative Database Schema Changes
34mLet's talk Databases in Python: SQLAlchemy and Alembic
21mDjango's Migrations: A Retrospective
25mUpdating Databases the GitOps Way
33mPeaceful Django Migrations with Efe Öge
57mDjangoCon 2008 Panel: Schema Evolution
08mDatabase as Code. Not only migrations