Limit Maximum Number of Sockets in Node.js: A 2026 Guide

Managing the number of sockets in a Node.js server is crucial for maintaining optimal performance and avoiding server overload. In this tutorial, you will learn how to set a limit on the maximum number of sockets your Node.js server can handle. This can help improve server reliability and performance, especially under heavy load.

Key Takeaways

• Understand the importance of socket management in Node.js.
• Learn how to set a maximum number of sockets using Node.js built-in features.
• Implement connection refusal for exceeding socket limits.
• Discover troubleshooting tips for common errors.

Introduction

Node.js is a popular platform for building scalable network applications. By default, Node.js can handle a large number of concurrent connections efficiently. However, there are situations where you might want to limit the number of simultaneous connections to your server. This can be particularly useful in scenarios where resources are constrained, or you want to prevent certain types of denial-of-service attacks.

In this guide, you will learn how to configure your Node.js server to limit the maximum number of sockets, effectively controlling the number of concurrent connections. This will help you maintain server stability and ensure a smooth experience for your users.

Prerequisites

• Basic understanding of Node.js and JavaScript.
• Node.js installed on your machine (version 18 or later recommended).
• A text editor like VS Code.

Step 1: Create a Basic Node.js Server

First, let's create a basic HTTP server using Node.js. This will serve as our starting point.

const http = require('http');

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

server.listen(3000, () => {
  console.log('Server is listening on port 3000');
});

This simple server listens on port 3000 and responds with "Hello, world!" to any incoming request.

Step 2: Set Maximum Number of Sockets

To limit the number of sockets, we can utilize Node.js's built-in server.maxConnections property. This property allows you to specify the maximum number of concurrent connections your server can handle.

server.maxConnections = 2; // Set the maximum number of concurrent connections

server.on('connection', (socket) => {
  console.log('A new connection was made by a client.');
});

By setting server.maxConnections = 2, we limit the server to handle only two concurrent connections at a time. Any additional connections will be queued until a slot becomes available.

Step 3: Implement Connection Refusal

To actively refuse new connections when the limit is reached, you'll need to monitor the number of active connections and respond accordingly. Unfortunately, Node.js doesn't provide a direct way to refuse connections beyond the maximum limit; they are queued by default. However, you can manually manage sockets and implement a custom logic to close excess connections.

let activeConnections = 0;

server.on('connection', (socket) => {
  if (activeConnections >= server.maxConnections) {
    socket.end('HTTP/1.1 503 Service Unavailable\n\n');
  } else {
    activeConnections++;
    socket.on('close', () => {
      activeConnections--;
    });
  }
});

In this code snippet, we track the number of active connections. If a new connection exceeds the limit, it is immediately closed with a 503 Service Unavailable response.

Step 4: Test Your Configuration

To test the configuration, you can use tools like curl or a web browser to make requests to your server. Open multiple terminal windows and run curl http://localhost:3000 to simulate concurrent connections. Observe how the server handles requests beyond the set limit.

Common Errors/Troubleshooting

• Connection Refused: Ensure that your server is running and listening on the correct port.
• Max Connections Not Working: Verify that server.maxConnections is set correctly and that your connection refusal logic is implemented properly.
• Server Crash: Check for syntax errors or unhandled exceptions in your code.

Frequently Asked Questions

Why limit the number of sockets?

Limiting sockets helps prevent server overload and ensures fair distribution of resources among connections.

Can this method prevent DDoS attacks?

While it helps manage connections, it is not a comprehensive solution for DDoS protection.

What happens to excess connections?

By default, they are queued. With custom logic, you can reject them with a response.

Frequently Asked Questions

Why limit the number of sockets?

Limiting sockets helps prevent server overload and ensures fair distribution of resources among connections.

Can this method prevent DDoS attacks?

While it helps manage connections, it is not a comprehensive solution for DDoS protection.

What happens to excess connections?

By default, they are queued. With custom logic, you can reject them with a response.