DEV Community

Cover image for 🟦🟩 Blue/Green Deployment Strategy
likhitha manikonda
likhitha manikonda

Posted on

🟦🟩 Blue/Green Deployment Strategy

#bluegreen #automation #devops #beginners

Blue/Green deployment is a simple way to update software without causing downtime or breaking things for users. You create two environments—Blue (current version) and Green (new version)—and switch traffic to Green only when it's ready.

🟦🟩 Blue/Green Deployment Strategy Explained for Absolute Beginners

Imagine you run a restaurant. You want to renovate the kitchen, but you can’t stop serving food. So, you build a second kitchen next door, test everything there, and once it’s perfect, you start cooking in the new kitchen and close the old one. That’s the idea behind Blue/Green deployment in software!

💡 What Is Blue/Green Deployment?

It’s a strategy used by developers to release new versions of software without downtime and with minimal risk. You maintain two identical environments:

  • Blue: The current live version that users are interacting with.
  • Green: The new version where updates are made and tested.

Once the Green version is ready and verified, you switch user traffic from Blue to Green. If something goes wrong, you can quickly switch back to Blue.

🛠️ How It Works (Step-by-Step)

  1. Blue is live: Users are using the Blue environment.
  2. Green is prepared: Developers deploy the new version to Green and test it thoroughly.
  3. Switch happens: Once Green is confirmed to be working, traffic is redirected from Blue to Green.
  4. Blue becomes backup: If issues arise, you can roll back by switching traffic back to Blue.

✅ Why Use It?

  • Zero downtime: Users don’t experience interruptions.
  • Safe rollbacks: You can revert to the old version instantly.
  • Better testing: You test the new version in a real environment before going live.

🚧 Things to Watch Out For

  • Database changes: If your update changes the database, rolling back might be tricky.
  • Cost: Running two environments can be more expensive.
  • Syncing data: You need to ensure both environments handle data consistently.

🧪 Real-Life Example

Let’s say you’re updating your online store. You deploy the new version to Green, test the checkout process, and once everything works, you switch users to Green. If payments fail, you switch back to Blue and fix the issue.

This strategy is widely used in cloud platforms like AWS, Azure, and Kubernetes. It’s a great way to deploy confidently and keep users happy.

Implementing a Blue/Green deployment strategy involves setting up two separate environments and managing traffic between them. Here's a beginner-friendly breakdown of how it's typically done:

🛠️ How Blue/Green Deployment Is Implemented

1. Set Up Two Identical Environments

  • Blue: The current live version of your app.
  • Green: A clone of Blue, where you’ll deploy the new version.
  • These can be separate servers, containers, or cloud environments.

2. Deploy the New Version to Green

  • Push your updated code, configurations, and database changes (if any) to the Green environment.
  • Run automated tests and manual checks to ensure everything works as expected.

3. Switch Traffic to Green

  • Use a load balancer or DNS switch to redirect user traffic from Blue to Green.
  • This switch can be instant or gradual (called canary release if done slowly).

4. Monitor the Green Environment

  • Watch for errors, performance issues, or user complaints.
  • Use logging and monitoring tools to track behavior.

5. Roll Back if Needed

  • If something goes wrong, switch traffic back to Blue.
  • Since Blue hasn’t changed, it acts as a safety net.

6. Retire or Update Blue

  • Once Green is stable, you can:
    • Delete Blue to save resources.
    • Or update Blue to become the next Green for future deployments.

🧰 Tools Commonly Used

  • Cloud Platforms: AWS (Elastic Beanstalk, EC2), Azure, Google Cloud
  • Containers: Docker, Kubernetes
  • CI/CD Pipelines: GitHub Actions, Jenkins, GitLab CI
  • Traffic Management: NGINX, HAProxy, AWS Route 53

Here’s how Blue/Green deployment is done on Kubernetes, step by step:

✅ 1. What is happening in Kubernetes?

  • Kubernetes manages Pods (your application containers).
  • For Blue/Green, you run two separate versions of your app:
    • Blue = current live version.
    • Green = new version you want to deploy.

✅ 2. How to implement Blue/Green in Kubernetes

  • Create two Deployments:
    • deployment-blue → points to the current version.
    • deployment-green → points to the new version.
  • Expose them via Services:
    • Each deployment can have its own Service (or share one with selective routing).
  • Routing control:
    • Use Ingress or API Gateway (like Gloo Proxy) to direct traffic.
    • Initially, 100% traffic goes to Blue.
    • When Green is ready, switch traffic gradually or all at once.

✅ 3. Steps

  1. Deploy Blue pods (live).
  2. Deploy Green pods (new version).
  3. Test Green internally (no external traffic yet).
  4. Update Ingress/Gloo Proxy routing:
    • Move traffic from Blue → Green.
  5. If issues occur, roll back by routing back to Blue.

✅ Why use Blue/Green?

  • Zero downtime during updates.
  • Quick rollback if something breaks.
  • Safe testing before going live.

Top comments (0)