Difference between revisions of "Blue-green deployment"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
* [[Red-black deployment]]s | * [[Red-black deployment]]s | ||
* [[Blue/Green deployment]] with [[CodeDeploy]] | * [[Blue/Green deployment]] with [[CodeDeploy]] | ||
| + | * [[AWS ECS deployments]] | ||
| + | * [[ArgoCD]] | ||
== Activities == | == Activities == | ||
| Line 19: | Line 21: | ||
== See also == | == See also == | ||
| + | * {{rolling}} | ||
* {{CD}} | * {{CD}} | ||
[[Category:DevOps]] | [[Category:DevOps]] | ||
Latest revision as of 09:11, 18 October 2024
wikipedia:Blue-green deployment
The CI/CD pipeline architecture creates a clone (green) of the live Elastic Beanstalk environment (blue). The pipeline then swaps the URLs between the two environments.
Consider creating a Blue/Green Deployment to minimize downtime during upgrades
Related[edit]
- Feature toggle
- Red-black deployments
- Blue/Green deployment with CodeDeploy
- AWS ECS deployments
- ArgoCD
Activities[edit]
See also[edit]
- Kubernetes deployments strategies, AWS ECS Rolling deployments, Blue-green deployment
- Deployment, CD, Spinnaker, AWS CodeDeploy, Tekton, Argo CD, Continuous Deployment, Continuous Delivery, Blue-green deployment, Red-black deployment, Feature toggle Continuous Delivery Foundation, ARA, A/b testing, Canary
Advertising:
