Cluster vs reverse proxy decision in Node.js - Quick Revision & Key Differences

Recall & Review

beginner

What is the main purpose of using a cluster in Node.js?

A cluster allows a Node.js application to use multiple CPU cores by creating child processes that share the same server port, improving performance and reliability.

beginner

What role does a reverse proxy play in a web application setup?

A reverse proxy sits in front of web servers, forwarding client requests to them. It can handle load balancing, SSL termination, caching, and security filtering.

intermediate

When should you choose a cluster over a reverse proxy in Node.js?

Choose a cluster when you want to maximize CPU usage within a single machine by running multiple Node.js processes to handle requests concurrently.

intermediate

Why might you use a reverse proxy instead of a cluster for scaling?

A reverse proxy can distribute traffic across multiple servers or services, not just processes on one machine, enabling horizontal scaling and better fault tolerance.

advanced

Can clusters and reverse proxies be used together? Explain.

Yes, clusters can be used to utilize multiple CPU cores on a single server, while a reverse proxy can distribute traffic across multiple servers running clusters, combining vertical and horizontal scaling.

What does a Node.js cluster primarily help with?

A Using multiple CPU cores on one machine

B Distributing traffic across multiple servers

C Caching static files

D Encrypting data between client and server

Clusters create child processes to use multiple CPU cores on a single machine.

Which of these is NOT a typical function of a reverse proxy?

A Load balancing

B SSL termination

C Request filtering

D Running multiple Node.js processes

Running multiple Node.js processes is done by clustering, not by a reverse proxy.

If you want to scale your app across multiple servers, what should you use?

A Cluster

B Reverse proxy

C Single Node.js process

D Local caching

A reverse proxy can distribute traffic across multiple servers for horizontal scaling.

Which setup improves CPU usage on a single machine?

A Cluster only

B Reverse proxy only

C Neither

D Both cluster and reverse proxy

Clusters create multiple processes to use all CPU cores on one machine.

What is a benefit of combining clusters with a reverse proxy?

A Automatic database backups

B Simpler codebase

C Improved vertical and horizontal scaling

D Less network traffic

Clusters handle multiple cores on one server (vertical scaling), reverse proxies distribute traffic across servers (horizontal scaling).

Explain the differences between a Node.js cluster and a reverse proxy and when to use each.

Think about how each helps handle more requests and where they fit in the system.

Describe a scenario where using both a cluster and a reverse proxy together makes sense.

Imagine a busy website running on several servers, each using clusters.

Practice

1. What is the main purpose of using a cluster in a Node.js application?

easy

A. To forward HTTP requests to different servers

B. To use multiple CPU cores by creating worker processes

C. To add security features like SSL termination

D. To cache static files for faster delivery

Solution

1. Step 1: Understand what a cluster does in Node.js

   A cluster creates multiple worker processes to use all CPU cores efficiently.

2. Step 2: Compare with other options

   Forwarding requests and adding security are tasks of a reverse proxy, not a cluster.

3. Final Answer:

   To use multiple CPU cores by creating worker processes -> Option B

4. Quick Check:

   Cluster = multiple CPU cores [OK]

Hint: Clusters = multiple CPU cores, reverse proxy = request forwarding [OK]

Common Mistakes:

• Confusing cluster with reverse proxy functions
• Thinking clusters handle security features
• Assuming clusters cache files

2. Which of the following is the correct way to create a cluster in Node.js?

easy

A. const cluster = require('cluster'); cluster.fork();

B. const proxy = require('proxy'); proxy.create();

C. const http = require('http'); http.listenCluster();

D. const cluster = require('cluster'); cluster.createServer();

Solution

1. Step 1: Recall Node.js cluster module usage

   The cluster module is required with require('cluster') and workers are created with cluster.fork().

2. Step 2: Check other options for correctness

   There is no proxy module by default, http.listenCluster() and cluster.createServer() are invalid methods.

3. Final Answer:

   const cluster = require('cluster'); cluster.fork(); -> Option A

4. Quick Check:

   cluster.fork() creates workers [OK]

Hint: Use cluster.fork() to create workers in Node.js [OK]

Common Mistakes:

• Using non-existent methods like cluster.createServer()
• Confusing proxy module with cluster
• Trying to call listenCluster() on http

3. Given this setup: a Node.js app uses a cluster with 4 workers and a reverse proxy in front. What is the main benefit of this combination?

medium

A. The cluster manages security, and the reverse proxy manages CPU usage

B. The cluster handles SSL termination, and the reverse proxy creates workers

C. The reverse proxy caches data, and the cluster forwards requests

D. The reverse proxy balances traffic, and the cluster uses all CPU cores

Solution

1. Step 1: Understand roles of cluster and reverse proxy

   The cluster allows Node.js to use multiple CPU cores by creating workers. The reverse proxy balances incoming traffic among servers.

2. Step 2: Eliminate incorrect roles

   SSL termination and security are usually handled by reverse proxies, not clusters. Clusters do not forward requests or cache data.

3. Final Answer:

   The reverse proxy balances traffic, and the cluster uses all CPU cores -> Option D

4. Quick Check:

   Cluster = CPU cores, Reverse proxy = traffic balance [OK]

Hint: Cluster for CPU, reverse proxy for traffic control [OK]

Common Mistakes:

• Swapping roles of cluster and reverse proxy
• Thinking cluster handles SSL or security
• Assuming reverse proxy creates workers

4. You wrote this code snippet to create a cluster but it crashes immediately:

const cluster = require('cluster');
cluster.fork();
require('http').createServer((req, res) => res.end('Hello')).listen(3000);

What is the likely cause?

medium

A. The worker process does not listen on a port

B. Missing a callback function in cluster.fork()

C. Not checking cluster.isMaster before forking

D. No error handling for server creation

Solution

1. Step 1: Analyze cluster usage

   The code calls cluster.fork() without checking if (cluster.isMaster). Both master and worker processes fork additional processes and attempt to bind to port 3000, causing port conflicts (EADDRINUSE) and crashes.

2. Step 2: Identify the problem

   The missing if (cluster.isMaster) check before forking leads to repeated forking and server creation attempts, causing the crash.

3. Final Answer:

   Not checking cluster.isMaster before forking -> Option C

4. Quick Check:

   Check cluster.isMaster before fork [OK]

Hint: Always check cluster.isMaster before forking [OK]

Common Mistakes:

• Calling cluster.fork() without isMaster check
• Assuming fork needs a callback
• Ignoring server listen port

5. You want to improve your Node.js app's performance and reliability. You decide to use both a cluster and a reverse proxy. Which setup best achieves this goal?

hard

A. Use a cluster to run multiple workers on all CPU cores, and a reverse proxy to distribute incoming requests and handle SSL

B. Use a reverse proxy to create worker processes, and a cluster to forward requests to other servers

C. Use a cluster to cache static files, and a reverse proxy to manage CPU usage

D. Use a reverse proxy to run multiple Node.js instances, and a cluster to balance traffic

Solution

1. Step 1: Identify cluster's role in performance

   Clusters run multiple worker processes to use all CPU cores, improving performance and reliability.

2. Step 2: Identify reverse proxy's role in traffic and security

   Reverse proxies distribute incoming requests, handle SSL termination, and add security features.

3. Step 3: Evaluate options

   Only Use a cluster to run multiple workers on all CPU cores, and a reverse proxy to distribute incoming requests and handle SSL correctly assigns cluster to CPU usage and reverse proxy to traffic distribution and SSL.

4. Final Answer:

   Use a cluster to run multiple workers on all CPU cores, and a reverse proxy to distribute incoming requests and handle SSL -> Option A

5. Quick Check:

   Cluster = CPU workers, Reverse proxy = traffic & SSL [OK]

Hint: Cluster for CPU workers, reverse proxy for traffic & SSL [OK]

Common Mistakes:

• Assigning reverse proxy to create workers
• Confusing caching with cluster role
• Swapping roles of cluster and reverse proxy