Nginx vs Node.js - reverse proxy for multiple web socket servers

I want to host MULTIPLE WEBSOCKETS node servers (separate processes). It can be> 1000 concurrent connections. I also want to register and monitor each connection and want to make it MEMORY effective. Is it a good idea to write a reverse proxy in node.js? Is it worse than Nginx, pure Erlang or Scala? Can Nginx handle 1000+ network connections? 1 connection freeze 1 nginx thread? How effective is memory?

+4
source share
2 answers

The simple answer is: nginx does not currently run HTTP / 1.1 upstream and therefore is definitely not a web site (and has no threads, but that's a different story). A simple user proxy based on node.js is probably a good solution. You could also create something in Java; There are many people who are now creating websockets services.

+4
source

You should consider pure nginx .

http://wiki.nginx.org/3rdPartyModules

0
source

Source: https://habr.com/ru/post/1334820/


All Articles