Atlas

One area hasn’t benefited from the DevOps movement as much: The database change process. It’s time to bring CI/CD to the database. Application release technology has come a long way in the past several years. It used to take weeks or even months to release new software. Now that organizations have adopted new workflows and processes, the time it takes to complete a release has been reduced to days and even hours. Database schema migrations are an essential task for every software project. There are several different reasons why updates to the database are required. New features require new attributes in existing tables or entirely new tables. Bug fixes may lead to changes in names or data types in the database. Performance issues that require additional indexes in the database. Even in organizations that have adopted DevOps, manual rework is the norm when it comes to database schema and stored procedure changes.

Define the desired schema of your database in a familiar and declarative syntax. Our open-source engine automatically generates migration plans that are verified during your team’s existing CI pipeline and safely deployed to production. Our platform rigorously simulates and analyzes each proposed change during your team’s existing CI flow to ensure no one accidentally breaks the database. Catch destructive changes, backward-incompatibility issues, accidental table locks and constraint violations way before they reach production. Deploy database schema changes as part of your continuous delivery pipelines with our Terraform or Helm integrations. Using our platform, you can safely execute changes that cannot be completely verified during CI, as they depend on the data in the target database.