Skip to content

Instantly share code, notes, and snippets.

@EliFuzz
Created July 19, 2023 06:55
Show Gist options
  • Save EliFuzz/5cc8550e701d7c2399e4956cfa0f3035 to your computer and use it in GitHub Desktop.
Save EliFuzz/5cc8550e701d7c2399e4956cfa0f3035 to your computer and use it in GitHub Desktop.
Pros & Cons: Blue-green deployment
Pros Cons
Zero-downtime deployment: can deploy a new version of the application without affecting the users or the service availability High resource consumption and cost: need to have two identical environments that run parallelly, which can consume twice as much resources and cost as a single environment
Easy rollback: can easily revert to the previous version of the application by switching back to the old environment in case of any issues or errors High synchronization and coordination challenges: need to keep both environments in sync with each other in terms of data, configuration and dependencies. You also need to coordinate with other teams or stakeholders when performing the switch
Low risk of failure and downtime: can perform thorough testing and verification on the new environment before switching it to live
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment