That's not their backend, it's just servicing a front-end feature.

It's doing what normally Erlang would have been used for, which answers the original question. It's a node.js deployment, and very early version one at that. I'm not really sure what your point is.

Plurk actually gave up on node after failing to optimize their service and went back to Netty (http://amix.dk/blog/post/19577). A better answer is this: https://github.com/joyent/node/wiki/Projects,-Applications,-...