Context So you have a typical project with a backend API and a frontend app built with React or Angular. You want to ensure that every time you push changes to production, they are thoroughly tested and deployed. To achieve this, you set up a CI/CD pipeline that handles the building, testing, and deployment processes automatically. At first, everything works smoothly, but as your project grows, you notice the pipeline is taking longer to complete.

So, you have database changes—either schema or data changes—that need to be implemented and rolled out across various environments. One approach could be to connect directly to each database server and execute scripts. However, you might not—and indeed, probably should not—have direct read/write access to certain environments like beta or production. Additionally, consider if a client posed the following questions; would you be able to easily respond? What is the state of the database in our Production environment?