Node.js cluster versus JXcore multithread

lunarcave wrote: post #2

You can partially mitigate the risks of single threaded Node by using clustering (although it's still tagged an experimental feature) [1]. Also, these worker threads can be made to respawn on a shutdown caused by - let's say - an unhandled exception as [2]. [1] http://nodejs.org/api/cluster.html [2] https://nadeesha.silvrback.com/setting-up-multiple-worker-th...

Well by experimental feature the Node.js team means that the API to access clustering features isn't set in stone - not the stability of the code.

Re: Node.js cluster versus JXcore multithread

#6

Post by camus2 » Thu, Apr 17, 2014, 3:53 PM UTC

stephenr wrote: post #3

I'm curious how either of these compare to say Passenger?

how can Passenger help with multi-threading/workers/... ? if a Passenger dev is nearby... i'm curious about it.

Re: Node.js cluster versus JXcore multithread

#7

Post by stephenr » Thu, Apr 17, 2014, 5:52 PM UTC

camus2 wrote: post #6

stephenr wrote: post #3

I'm curious how either of these compare to say Passenger?

how can Passenger help with multi-threading/workers/... ? if a Passenger dev is nearby... i'm curious about it.

Passenger can manage multiple node processes for the same "app" automatically.

So while it isn't multi-threaded it can achieve some of the same goals (better use of multiple cores to serve more requests)