> you also have to manage a cluster of processes on every one of those machines! you just set a number of cluster/processes per machine, that's it. there is no

> you also have to manage a cluster of processes on every one of those machines! you just set a number of cluster/processes per machine, that's it. there is no dedicated management for clusters on multiple cores. That's the benefit of clustering as scaling method with Node: one method scales on multiple cores and/or multiple machines. Not go-routines and clustering like Go—the application design will be much more coherent instead of using go-routines AND cluster where a reference implementation is missing (but I am repeating myself). > as the cluster of machines will need to be managed by yourself or a third party like Heroku. Rather you should write your own cluster management in Node. You could take some kind of a web server or Heroku that starts all the app server processe per connection but that's old-school.