Cluster vs reverse proxy decision in Node.js - Hands-On Comparison

Cluster vs Reverse Proxy Decision in Node.js

📖 Scenario: You are building a simple Node.js web server that needs to handle multiple requests efficiently. You want to learn how to use Node.js cluster module to create worker processes and also understand how a reverse proxy like Nginx can help distribute requests.

🎯 Goal: Build a Node.js server that uses the cluster module to create worker processes. Then add a configuration variable to simulate a reverse proxy setup decision. Finally, implement logic to start the server differently based on whether clustering or reverse proxy is chosen.

📋 What You'll Learn

Create a basic HTTP server using Node.js

Use the cluster module to create worker processes

Add a configuration variable to choose between cluster mode or reverse proxy mode

Implement conditional logic to start the server based on the chosen mode

💡 Why This Matters

🌍 Real World

Node.js servers often need to handle many requests efficiently. Using clustering allows the server to use multiple CPU cores. Reverse proxies like Nginx can also distribute requests to multiple server instances.

💼 Career

Understanding clustering and reverse proxy setups is important for backend developers to build scalable and reliable web applications.

1

Create a basic HTTP server

Create a variable called http that requires the http module. Then create a server using http.createServer that responds with 'Hello from worker' for every request. Assign the server to a variable called server.

Node.js

const http = require('http');
// Your code here

Need a hint?

Use require('http') to import the HTTP module. Then use http.createServer with a callback that sends a plain text response.

2

Add a configuration variable for mode selection

Add a constant called useCluster and set it to true. This variable will decide if the server runs in cluster mode or reverse proxy mode.

Node.js

const http = require('http');

const server = http.createServer((req, res) => {
  res.writeHead(200, { 'Content-Type': 'text/plain' });
  res.end('Hello from worker');
});

// Your code here

Need a hint?

Declare a constant named useCluster and assign it the boolean value true.

3

Implement cluster logic to create workers

Require the cluster and os modules as cluster and os. Then write an if statement that checks if useCluster is true and cluster.isMaster is true. Inside it, create worker processes equal to the number of CPU cores using os.cpus().length. Otherwise, start the server listening on port 3000.

Node.js

const http = require('http');

const server = http.createServer((req, res) => {
  res.writeHead(200, { 'Content-Type': 'text/plain' });
  res.end('Hello from worker');
});

const useCluster = true;

// Your code here

Need a hint?

Use cluster.isMaster to check if the current process is the master. Use os.cpus().length to get CPU count. Fork workers in a loop. Start server in the else block.

4

Add reverse proxy mode handling

Modify the if condition to check if useCluster is false. In that case, start the server listening on port 3000 directly. This simulates running behind a reverse proxy where clustering is handled externally.

Node.js

const http = require('http');
const cluster = require('cluster');
const os = require('os');

const server = http.createServer((req, res) => {
  res.writeHead(200, { 'Content-Type': 'text/plain' });
  res.end('Hello from worker');
});

const useCluster = true;

// Your code here

Need a hint?

Add an else if block to check when useCluster is false and start the server. This simulates reverse proxy mode.