A blog series some of you might find interesting

[Francois Marier]

As some of you might know, I work on Mozilla Persona, which is running
Node.JS on the back-end.

We have started a technical blog series about the choices we made and
various problems we solved:

https://hacks.mozilla.org/category/a-node-js-holiday-season/

Right now we have a post on memory leaks and one on CPU-bound processes.
Next week, there will be one on doing secure client-side sessions.

Cheers,
Francois

[Andrew Chilton]

Hi Francois,

> https://hacks.mozilla.org/category/a-node-js-holiday-season/

Thanks for the link for the list. :)

I read both of those articles recently (a week or so back for #1 and
this morning for #2). They're great reading and I have to play with
memwatch soon to make sure I'm not leaking memory like a sieve!

On the point of the 2nd post, I did also wonder if another solution is
to send messages to other servers - which can scale either locally on
one box or starting up a load of them on multiple boxes. Node.js is
great for just having a bunch of small servers talking to each other
and it'll save the cost of starting up new processes (though I presume
compute-cluster does some pooling of child processes). I may try and
mock something up at one stage, probably using dnode.

* https://github.com/substack/dnode

(Ok, as I wrote this, I decided to also leave a comment there too.)

Cheers,
Andy

--
contact: Andrew Chilton
website: http://www.chilts.org/blog/