I've searched a lot to figure out this question, but I didn't get clear explanation. Is there only one difference thing that clustered app can be scaled out and forked app cannot be?
PM2's public site explains Cluster mode can do these feature but no one says about pros of Fork mode (maybe, it can get NODE_APP_INSTANCE
variable).
I feel like Cluster might be part of Fork because Fork seems like to be used in general. So, I guess Fork means just 'forked process' from the point of PM2 and Cluster means 'forked process that is able to be scaled out'. Then, why should I use Fork mode?
The main difference between fork_mode
and cluster_mode
is that it orders pm2 to use either the child_process.fork api or the cluster api.
Take the fork
mode as a basic process spawning. This allows to change the exec_interpreter
, so that you can run a php
or a python
server with pm2. Yes, the exec_interpreter
is the "command" used to start the child process. By default, pm2 will use node
so that pm2 start server.js
will do something like:
require('child_process').spawn('node', ['server.js'])
This mode is very useful because it enables a lot of possibilities. For example, you could launch multiple servers on pre-established ports which will then be load-balanced by HAProxy or Nginx.
The cluster
will only work with node
as it's exec_interpreter
because it will access to the nodejs cluster module (eg: isMaster
, fork
methods etc.). This is great for zero-configuration process management because the process will automatically be forked in multiple instances.
For example pm2 start -i 4 server.js
will launch 4 instances of server.js
and let the cluster module handle load balancing.