A blue-green deployment is a popular technique for DevOps teams who want to reduce the risk of downtime or errors associated with deployments to production environments. In a blue-green deployment scenario, you maintain two identical production environments (called blue and green) that differ only with respect to the new changes being deployed. Only one environment is ever live at a time, and traffic is directed between these environments as part of the deployment. This technique works great for stateless apps without any data, but is significantly more challenging for stateful apps like databases because you must maintain two copies of production data. Portworx solves this data management problem with PX-Motion..
Problems with blue-green deployments today:
- Creating multiple copies of production data is difficult and error prone
- Isolating a single container’s data for copying to new environment is difficult with VM-optimized data management toolss
- In order for Kubernetes to seamlessly start up your apps in new environment, you also need to move configuration information, in addition to data