https://github.com/damiancipolat/nodejs-message-send-study
In this project I analyze different ways to create a distributed message processing backend using Node.js and sockets
https://github.com/damiancipolat/nodejs-message-send-study
balancer load nodejs socketio sockets
Last synced: about 1 month ago
JSON representation
In this project I analyze different ways to create a distributed message processing backend using Node.js and sockets
- Host: GitHub
- URL: https://github.com/damiancipolat/nodejs-message-send-study
- Owner: damiancipolat
- Created: 2019-02-20T05:18:00.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2019-03-30T04:50:32.000Z (about 7 years ago)
- Last Synced: 2025-05-20T01:13:29.411Z (about 1 year ago)
- Topics: balancer, load, nodejs, socketio, sockets
- Language: JavaScript
- Homepage:
- Size: 896 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Message processor
Examples and techniques of how to create a nodejs message processor through a permanent socket.
**Chapter list:**
- **[Model I]** simple client / server
- **[Model II]** client / master-worker server
- **[Model III]** client / master-worker server + custom socket balancer
- **[Model IV]** client / master-worker server + NGINX
[Model I]:https://github.com/damiancipolat/Node-MSG-Processor#model-i
[Model II]:https://github.com/damiancipolat/Node-MSG-Processor#model-2
[Model III]:https://github.com/damiancipolat/Node-MSG-Processor#model-3
[Model IV]:https://github.com/damiancipolat/Node-MSG-Processor#model-4
## Model I:
A single process with a server that receive and process the messages.
**Stress test:**
Process done with 3k messages.
**To run:**
```js
$ cd model-1
$ npm install
$ npm start
```
## Model 2:
A single process with a server that receive and process the messages.
**Stress test:**
Process done with 6k messages.
**To run:**
```js
$ cd model-2
$ npm install
$ npm run server
$ npm run client
```
## Model 3:
A model defined, that is ready to scale horizontal. This model use the model II with a load balancer in the front, this module have a particular beahaviour, function as an apirest that return a url of one server that is defined in his server list.
**Stress test:**
Process done with 10k messages.
**To run:**
```js
$ cd model-3
#To start server in a port.
$ npm run server 8080
#To start client, define server url and amount of request.
$ npm run client 100 http://localhost:8080
```
### Using custom socket balancer:
**To run:**
```js
$ cd model-3
#To start client
$ npm run client
#To start server
$ npm run server
#To start balancer
$ npm run balancer
```
## Model 4:
**Using NGINX as socket balancer**, This show how to use NGINX as socket load balancer. In productive environemts, I thinks that use NGINX is the best option instead of use my example of the previouse example, because is a very eficient and confiable product so is a good option to use in every project.
I'm following this link: https://www.digitalocean.com/community/tutorials/how-to-develop-a-node-js-tcp-server-application-using-pm2-and-nginx-on-ubuntu-16-04
### Diagram:
### Basic example: (client / NGINX / Server) without load balancer.
This example create a Nodejs socket server listen connections in the port **8081** and set the NGINX in the middle receiving connections in the port 8000 and by pass them to the port 8081, for other hand there are a client process that sent data to nginx. Pleas thake a look at the file nginx.conf
**nginx.conf**
```js
...
stream {
server {
listen 8000;
proxy_pass 127.0.0.1:8081;
proxy_protocol on;
}
}
```
**To run:**
```js
$ cd model-4/basic
#To start server
$ pm2 start server.js
#To start nginx
$ sudo systemctl restart nginx
#To start client
$ npm run client
#To view process running
$ pm2 list
```
#### Another configuration, could be /etc/nginx/sites-enabled/default
```js
server {
listen 80;
server_name 127.0.0.1;
location / {
proxy_pass http://127.0.0.1:8081;
proxy_redirect off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
```
### NGINX as load balancer:
I get the nginx configuration from:
https://socket.io/docs/#using-with-node-http-server
https://www.digitalocean.com/community/tutorials/how-to-develop-a-node-js-tcp-server-application-using-pm2-and-nginx-on-ubuntu-16-04
#### Configuration /etc/nginx/nginx.conf
Take care of set "stream" in nginx.conf.
```js
events{
}
stream {
# Load balancer configuration
upstream exampleApp {
# One failed response will take a server out of circulation for 20 seconds.
server 127.0.0.1:8081;
server 127.0.0.1:8082;
server 127.0.0.1:8083;
}
server {
listen 8000;
proxy_pass exampleApp;
proxy_protocol on;
}
}
```