Zero-downtime deployment concept in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is zero-downtime deployment?

Zero-downtime deployment is a method of updating an application without stopping the service or causing any interruption to users.

beginner

Why is zero-downtime deployment important for web applications?

It ensures users can keep using the app without interruptions, improving user experience and avoiding lost traffic or revenue.

intermediate

Name one common technique used in zero-downtime deployment with Express apps.

Using a process manager like PM2 to reload the app gracefully without dropping connections.

intermediate

How does a load balancer help achieve zero-downtime deployment?

It directs traffic to healthy instances and can route users away from servers being updated, allowing updates without service interruption.

intermediate

What is a graceful shutdown in the context of zero-downtime deployment?

It means the server stops accepting new requests but finishes handling ongoing requests before shutting down, preventing dropped connections.

What does zero-downtime deployment prevent?

A Faster server startup

B More memory usage

C Service interruptions during updates

D Longer downtime

Zero-downtime deployment prevents service interruptions during updates, keeping the app available.

Which tool can help reload an Express app without dropping connections?

A PM2

B Git

C Webpack

D Nodemon

PM2 can reload apps gracefully, enabling zero-downtime deployment.

What role does a load balancer play in zero-downtime deployment?

A Caches static files

B Routes traffic to healthy servers

C Manages database connections

D Compiles code

Load balancers route traffic to healthy servers, helping avoid downtime during updates.

What is a graceful shutdown?

A Ignoring ongoing requests

B Immediately killing the server process

C Restarting the server every minute

D Stopping new requests but finishing current ones before shutdown

Graceful shutdown stops new requests but completes ongoing ones to avoid dropped connections.

Which of these is NOT a benefit of zero-downtime deployment?

A Longer maintenance windows

B No service interruptions

C Improved user experience

D Continuous availability

Zero-downtime deployment aims to reduce maintenance windows, not make them longer.

Explain how zero-downtime deployment works in an Express app environment.

Think about how the app keeps running while updating.

Describe why zero-downtime deployment is important for user experience and business.

Consider what happens if the app goes offline during updates.

Practice

1. What is the main goal of zero-downtime deployment in an Express app?

easy

A. Keep the app running without interruption during updates

B. Stop the app completely before updating

C. Restart the server manually after every update

D. Disable all routes temporarily during deployment

Solution

1. Step 1: Understand zero-downtime deployment purpose

   It aims to keep the app available and responsive while new code is deployed.

2. Step 2: Compare options with this goal

   Only keeping the app running without interruption matches zero-downtime deployment.

3. Final Answer:

   Keep the app running without interruption during updates -> Option A

4. Quick Check:

   Zero-downtime = no interruption [OK]

Hint: Zero downtime means no app stops during update [OK]

Common Mistakes:

• Thinking the app must stop to update
• Confusing manual restart with automatic update
• Assuming routes must be disabled during deployment

2. Which Node.js module helps run multiple instances of an Express app for zero-downtime deployment?

easy

A. http

B. path

C. fs

D. cluster

Solution

1. Step 1: Identify module for multiple app instances

   The cluster module allows running multiple worker processes of the app.

2. Step 2: Verify other modules' purposes

   http handles server requests, fs handles files, path handles file paths, none manage multiple processes.

3. Final Answer:

   cluster -> Option D

4. Quick Check:

   Multiple instances = cluster module [OK]

Hint: Cluster module manages multiple workers [OK]

Common Mistakes:

• Choosing http for multiple processes
• Confusing fs or path with process management
• Not knowing cluster exists

3. Given this code snippet using cluster in Express, what happens when a worker crashes?

const cluster = require('cluster');
const express = require('express');
if (cluster.isMaster) {
  cluster.fork();
  cluster.on('exit', (worker) => {
    console.log('Worker died, starting a new one');
    cluster.fork();
  });
} else {
  const app = express();
  app.get('/', (req, res) => res.send('Hello'));
  app.listen(3000);
}

medium

A. A new worker starts automatically

B. No new worker starts, app crashes

C. The app stops completely

D. The master process crashes

Solution

1. Step 1: Analyze cluster exit event handler

   When a worker exits, the master logs a message and forks a new worker.

2. Step 2: Understand effect on app availability

   Replacing crashed workers keeps the app running without downtime.

3. Final Answer:

   A new worker starts automatically -> Option A

4. Quick Check:

   Worker crash triggers new worker fork [OK]

Hint: cluster.on('exit') forks new worker on crash [OK]

Common Mistakes:

• Thinking app stops when worker dies
• Assuming master process crashes
• Missing automatic restart logic

4. Identify the error in this zero-downtime deployment code snippet:

const cluster = require('cluster');
const express = require('express');
if (cluster.isMaster) {
  cluster.fork();
  cluster.on('exit', () => {
    console.log('Worker died');
  });
} else {
  const app = express();
  app.listen(3000);
}

medium

A. Using cluster.isMaster instead of cluster.isWorker

B. Missing code to restart worker on exit

C. Express app should be created in master process

D. app.listen should be outside else block

Solution

1. Step 1: Check cluster exit event handler

   The exit event logs a message but does not fork a new worker.

2. Step 2: Understand impact on zero-downtime

   Without restarting workers, the app loses capacity and may cause downtime.

3. Final Answer:

   Missing code to restart worker on exit -> Option B

4. Quick Check:

   Exit handler must fork new worker [OK]

Hint: Restart workers on exit to avoid downtime [OK]

Common Mistakes:

• Not restarting workers after exit
• Confusing master and worker roles
• Placing app.listen in wrong process

5. You want to deploy a new version of your Express app without downtime. Which approach best achieves this?

1. Use cluster to run multiple workers
2. On update, fork new workers with new code
3. Gracefully disconnect old workers after new ones are ready
4. Restart the entire server process immediately

Which steps should you follow?

hard

A. Steps 1 and 4 only

B. Only step 4

C. Steps 1, 2, and 3

D. Steps 2 and 4 only

Solution

1. Step 1: Understand zero-downtime deployment best practices

   Running multiple workers (step 1) allows traffic to continue during updates.

2. Step 2: Deploy new code by forking new workers (step 2) and gracefully disconnect old ones (step 3)

   This ensures no requests are dropped and old workers finish their tasks.

3. Step 3: Avoid immediate server restart (step 4) as it causes downtime

   Restarting the whole server stops all workers at once, causing downtime.

4. Final Answer:

   Steps 1, 2, and 3 -> Option C

5. Quick Check:

   Fork new workers and gracefully disconnect old [OK]

Hint: Fork new workers before disconnecting old ones [OK]

Common Mistakes:

• Restarting server immediately causing downtime
• Not gracefully disconnecting old workers
• Skipping multiple worker setup