There is an application implemented on node.js which is a REST API + client for it using backbone.js . The application will be used only within the local network. How expedient is deployment using nginx / apache ? Users working with the application will be no more than 200. Should regular node.js tools cope with such a load?

  • and how do you see the use of nginx or apache? What tasks could be solved with their help? - nörbörnĂ«n
  • load balancing as an option, the design of "normal" links - for example, application1 application2 . All this to “hang” on the default port (80) that nginx would manage by proxying requests already in accordance with the configured configurations. Well and in many manuals this question rises, so I decided to test for a start for a start. - kandellak
  • one
    balancing : are you going to pick up several instances of the node and balance between them? normal links : why not immediately make normal routers? Port 80 can listen and node. if only these tasks (rest api) then nginx is just an extra entity. but maybe there is something you don’t write about: static, caching, etc.? - nörbörnën
  • that's right, several instances of the node and balance between them, questions about statics and caching have not even arisen so far and therefore I do not consider them, I just mostly worry about using a regular web server, for example, in the same RoR / Django / Mojolicious regular web servers as a rule, they are single-threaded and are intended primarily for testing and development. - kandellak
  • one
    cluster can be used to process requests in several streams. nginx / apache, apparently, will not improve anything here. - nörbörnën

0