Blue-Green Deployment Readiness

In this lesson, you will learn how to structure your Node.js application so that traffic can be shifted between two identical environments without dropping active requests.

The Blue-Green Concept

"Blue-Green" deployment is a strategy where you run two identical production environments. At any time, only one (e.g., Blue) serves live user traffic, while the other (e.g., Green) runs your new version. To achieve zero-downtime, your server must be "deployment-ready," meaning it can stop accepting new requests while finishing the ones already in progress.

Graceful Transitioning

When a deployment triggers a switch, your server needs to stop listening for new connections while allowing existing requests to complete. In Node.js, this is achieved by using server.close() to stop the listener and implementing a state machine to track active requests.

If you don’t do this, users might receive a "Connection Refused" error the moment your process terminates during a switch.

Implementation Example

Your server must listen for a termination signal (like SIGTERM) to trigger this graceful shutdown:

const http = require('http');

const server = http.createServer((req, res) => {
  // Application logic
  res.end('Deployment transition successful');
});

server.listen(3000);

// Transition state management
process.on('SIGTERM', () => {
  console.log('Transitioning: Closing server...');
  
  // Stops accepting new requests, but waits for active ones to finish
  server.close(() => {
    console.log('Traffic transitioned: Server stopped safely.');
    process.exit(0);
  });
});

Why This Matters

By integrating this into your Cloud Native Server Design and using your Server-Side State Machines, you ensure that the transition between environments is invisible to the user. The Asynchronous Proxy Buffering we discussed earlier helps here, as it can hold requests in a queue while the "Green" environment completes its startup cycle and signals readiness.

When your load balancer (or service router) sees that the new environment is ready, it routes traffic away from the "Blue" environment, sending a SIGTERM to the old processes. Because you've configured the server to wait, no user request is left hanging in the middle of a transaction.

Key Takeaway: Blue-Green readiness requires your Node.js application to handle graceful shutdowns so that active requests can finish before the process exits during a traffic switch.