Real-World Concurrency (2008)

Re:Real-World Concurrency (2008) by kaoD on Wednesday March 06, 2013 @07:03AM (#5330686)

And that's why I love Node.js: the single-threaded concurrency (or should I say non-concurrency?) is built-in in the execution model. Building your architecture decoupled from the ground up is useful, and Node.js does a great job at it.

I found Redis is an awesome middleware for MQ purposes. Its builtin PubSub system, blocking POPs and amazing speed make it a perfect fit.

But beware: it's easy to get it wrong and make the system a tangled mess of messages. Just make sure the message dispatch overhead is worth it.

[ Parent | on HN ]

Re:Real-World Concurrency (2008) by fforw on Wednesday March 06, 2013 @09:58AM (#5331427)

Is node actually able to use more than one core now?

[ Parent | on HN ]

Re:Real-World Concurrency (2008) by DonPellegrino on Wednesday March 06, 2013 @12:19PM (#5332287)

It has been able to for a while! Check out the cluster module, processes listening to the same port are load balanced and communication between processes is obviously (since each process only has 1 thread due to the event loop) done by message passing.

[ Parent | on HN ]

Re:Real-World Concurrency (2008) by kaoD on Friday March 08, 2013 @06:54AM (#5342955)

Technically spakeaing: no, and it never will. Single-threading is by design, so the best bet is to run several processes, each using one core (see the other answer to your comment).

[ Parent | on HN ]