Multi-threaded Web Server based in Node.js

CK CK 3788 
Created at  
867 0 0

Node.js is inherently single-threaded, meaning it runs on a single thread by default. However, you can create a multi-threaded server using the worker_threads module, which allows you to run JavaScript code in parallel threads, or by using the cluster module to take advantage of multiple CPU cores.

Here's an example using the cluster module to create a multi-threaded server:

 

Multi-Threaded HTTP Server with cluster

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

// Get the number of CPU cores
const numCPUs = os.cpus().length;

if (cluster.isMaster) {
  console.log(`Master ${process.pid} is running`);

  // Fork workers (one per CPU core)
  for (let i = 0; i < numCPUs; i++) {
    cluster.fork();
  }

  // Listen for dying workers and replace them
  cluster.on('exit', (worker, code, signal) => {
    console.log(`Worker ${worker.process.pid} died`);
    cluster.fork();
  });
} else {
  // Workers can share any TCP connection, in this case, an HTTP server
  http.createServer((req, res) => {
    res.writeHead(200);
    res.end('Hello, World!\n');
  }).listen(3000);

  console.log(`Worker ${process.pid} started`);
}

 

How it works:

  • cluster.isMaster: The code checks if the current process is the master process. If it is, the master process will fork worker processes.
  • cluster.fork(): This method is used to create a new worker process. The number of workers is typically set to the number of CPU cores available, so each core can handle a separate process.
  • Worker processes: Each worker runs a copy of the server code. They all share the same server port and can handle requests concurrently.
  • cluster.on('exit', ...): This event listener ensures that if a worker dies, the master process will start a new worker to replace it.

 

Running the multi-threaded server:

  1. Save the code to a file, e.g., clustered-server.js.
  2. Run the server using Node.js:

    node clustered-server.js
    
  3. The server will listen on port 3000, and you will see multiple worker processes han
Tags Multi-Threaded Web Server Node.js Web Server Thread Application Facebook X
Comments 0
Similar posts
  1. A basic HTTP server based in Node.js
    544
  2. Node.js-based Web Server supporting multiple path
    604
  3. Trackback module used for Python Threading debugging
    847
  4. Rust Thread Example
    346
  1. Get client IP address and user agent in Node.js
    1,531
  2. forEach method in JavaScript when working with arrays
    667
  3. CRC32B function code in Javascript
    1,846
  4. A simple Javascript class example with static method for Node.js
    662
  5. Setting a Common Path for require() in Node.js
    1,007
  6. Import all JS files in a specific folder for Node.js programming
    1,733
  7. A simple example to access a PostgreSQL database in Node.js
    1,101
  8. Node.js code example to access Google BigQuery
    1,183
  9. Investigation on package.js for Node.js source code
    824
  10. Using MySQL in Node.js
    485
  11. A Node.js script that checks if a module is installed before requiring it
    774
  12. Worker Threads and Mutual Exclusion in Node.js
    466
  13. Using a module in the external class itself without creating an instance in Node.js
    350
  14. Node.js external modules
    434
Recently updated
  1. Google OAuth Token Expiration: Causes and Solutions
    31
  2. Why 100% SEO Guarantees Better User Engagement and How to Achieve It in Your Service
    57
  3. Why SPF and DKIM Are Essential for Linux Email Servers?
    51
  4. How do I create animated background for Google Meet?
    23,256
  5. MaxMind GeoLite2 vs. DB-IP Lite vs. ip-api.com: Choosing the Right Free IP Geolocation Solution
    273
  6. Meet Valkey: Why Redis Changed Its License, Why Valkey is Better, and How to Use It as a Drop-in Replacement
    105
  7. How Rogue Web Scrapers Are Stealing My Content and Destroying My Server
    170
  8. Array of arguments passed to script in PHP
    99
  9. Invalid Auction Storms in Ad Tech
    108
  10. Building MRC-Compliant Instrumentation in Ad Tech: Implementation Steps and Key Challenges
    209
  11. The Two Clocks of Ad Server Architecture
    78
  12. Frequency Cap Architecture Overview
    527
  13. Collecting Proof-of-Play from 100,000 Screens
    154
  14. Vector Search in Relational Databases (RDBs): Trends & Usage Environments
    303
  15. What is RedisVL?
    117
  16. Designing a Skill Registry Architecture: Minimize Token Usage and Maximize AI Performance
    247
  17. TPU & GPU Cluster Management Tools
    258
  18. The Concept of Scaffolding in AI Agents
    245
  19. Beyond Static Pipelines: Architecting LLM Multi-Agent Systems for Autonomous Workflow Orchestration
    599
  20. AI-DLC vs. AI-SDLC: Model-Centric vs. System-Centric AI Development
    269
  21. Fine-Tuning Open-Weight LLMs: Training, Licensing, and Deploying Custom Models with Ollama
    355
  22. Inside the Next-Generation Streaming Architecture: Ultra-Low Latency, SGAI, and AI Codecs
    207
  23. Machine Learning: Training vs. Ranking
    231
  24. The Continuous Learning Machine: Designing a Loop That Actually Turns
    229
  25. The Next-Gen Low-Latency Standards: LL-HLS & MoQ
    204
  26. Designing a Data Curation System Around a Vector Database
    230
  27. Extracting Context from Live Video: The Architecture Got Simpler When We Stopped Building Features
    263
  28. The New Ad Stack Behind Live Sports Streaming: Inside SGAI, EABN, and the Standards Race to Fix Live Monetization
    674
  29. Designing MLOps Architectures to Handle Seasonal Data Drift in EV Fleet Models
    201
  30. From 15 to 40+ FPS: Accelerating PyTorch Object Detection on Automotive ECUs
    233