Answer the question
In order to leave comments, you need to log in
Node.JS - forever vs upstart+monit?
Good evening everyone!
First, a little introductory part - there is an application - express + socket.IO (yes, like everyone else :). There is haproxy as a reverse proxy. The application scales across n servers. On each server cluster is used. So actually the question is: what is preferable to use for the "eternal" operation of the node? Of the advantages of forever, I see only a very simple use - 1 command and it's done. upstart + monit - more difficult (slightly) configurable + monit collects statistics about the state of the operating system, that's all. Which of these performs best in production? Can anyone share some tricks? I'm afraid for forever - it's also essentially a node server, can't it happen that it hangs for the company with the main server in case of mega-popularity?
If someone considers himself a node specialist or just has something to say - please hit the PM, there are a whole bunch of questions, you don’t want to pull stackoverflow or habra for the sake of every little thing =)
Thanks in advance to everyone!
Answer the question
In order to leave comments, you need to log in
I used supervisord.org for a couple of years , it worked without problems, and, in principle, a well-known thing for securing anything from falls.
There was already a similar question, I suggested there:
Runit (but this is an analogue of supervisord), it’s very easy to launch in one line, it can keep a log, run processes from the user, in case of a process crash, raise it, replace init.d scripts. As far as I remember, it is written in C and eats a minimum of resources.
pm2 - for sale it's the best, from the pros - simplicity, load balancer for web applications (express based), built-in monitoring with an excellent API.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question