blue-green deployment

Deployment & Operations

Meaning

A release management strategy that maintains two identical production environments (blue and green) to enable zero-downtime releases and instant rollback by switching traffic between them.

Primary Function

Enable zero-downtime deployments and immediate rollback by switching traffic between identical environments.

Communicative Purpose

Refer to the blue-green deployment strategy when discussing release processes, risk mitigation, and infrastructure planning.

Pattern

Adjective-noun compound (color adjective + noun)

Core Structure

[color]-deployment where the color indicates a parallel environment

Função primária

Enable zero-downtime deployments and immediate rollback by switching traffic between identical environments.

Propósito comunicativo

Refer to the blue-green deployment strategy when discussing release processes, risk mitigation, and infrastructure planning.

Situações de gatilho

Planning a production release requiring zero downtime; needing a quick rollback capability; managing stateful services where downtime is costly.

Contextos

DevOps, continuous delivery pipelines, cloud infrastructure (AWS, Azure, GCP), Kubernetes deployments, microservices architectures.

Padrão

Adjective-noun compound (color adjective + noun)

Estrutura central

[color]-deployment where the color indicates a parallel environment

Slots de substituição

[color1]/[color2] deployment (e.g., red‑black, blue‑green)

Colocados típicos

deployment
environment
traffic switch
load balancer
zero downtime
rollback
cutover

Substituições comuns

red‑black deployment
blue‑green release
A/B deployment

Erros comuns

Assuming it requires double the hardware at all times; confusing with canary releases; believing it eliminates all risk; thinking it only applies to web traffic.

Similar / contraste

canary release (gradual traffic shift), rolling update (incremental node updates), recreate (full shutdown/restart), feature flags (toggle features without redeploy)

Interferências

May be confused with feature flagging; ensure environments are truly identical (config, data, dependencies); traffic switching must be atomic to avoid split‑brain.

Família do chunk

deployment strategies
release management
DevOps practices
release patterns

Nuance

Requires near‑identical environments; data synchronization strategies needed for stateful components; cutover is typically DNS or load‑balancer reconfiguration.

Efeito pragmático

Signals expertise in modern release engineering; conveys commitment to reliability and minimal user impact.

Dica de memória

Imagine two identical pools of water, blue and green; you switch the flow from one to the other instantly.

Nota

Both environments must share identical configurations, database schemas, and external dependencies to prevent inconsistencies when traffic is switched during the cutover.

Upgrade path

Canary release or feature flagging for more fine‑grained control

Frequência: HighFormulaicidade: FixedTipo de construção: compound noun (color compound + noun)Prioridade de aquisição: Active recallPrioridade de output: BothTag de espaçamento: Medium-term

Examples

apiVersion: apps/v1 kind: Deployment metadata: name: web-blue spec: replicas: 3 selector: matchLabels: app: web color: blue template: metadata: labels: app: web color: blue spec: containers: - name: web image: myapp:v2 --- apiVersion: v1 kind: Service metadata: name: web-service spec: selector: app: web color: blue # points to blue environment ports: - port: 80 targetPort: 8080 --- # Switch traffic to green by patching the service selector to color: green

resource "aws_elastic_beanstalk_application" "app" { name = "myapp" } resource "aws_elastic_beanstalk_environment" "blue" { name = "myapp-blue" application = aws_elastic_beanstalk_application.app.name solution_stack_name = "64bit Amazon Linux 2018.03 v2.11.4 running Docker" } resource "aws_elastic_beanstalk_environment" "green" { name = "myapp-green" application = aws_elastic_beanstalk_application.app.name solution_stack_name = "64bit Amazon Linux 2018.03 v2.11.4 running Docker" } # Switch CNAME from blue to green resource "aws_elastic_beanstalk_environment" "swapped" { name = aws_elastic_beanstalk_environment.green.name # In practice, use `aws elasticbeanstalk swap-environment-cnames` via null_resource or local-exec }

#!/usr/bin/env bash # Docker Compose blue‑green deployment # Start blue stack docker-compose -f docker-compose.blue.yml up -d # Start green stack (identical config) docker-compose -f docker-compose.green.yml up -d # Switch nginx upstream: replace upstream blue with green sed -i 's/blue/green/' /etc/nginx/conf.d/upstream.conf nginx -s reload # Verify traffic, then stop blue if needed docker-compose -f docker-compose.blue.yml down