On Saturday, December 6, 2014 9:30:24 PM UTC+5:30, Aria Stewart wrote: > > > > On 6 Dec 2014, at 03:03, Harry Simons <[email protected] <javascript:>> > wrote: > > > > 2. To use multi-cores, I can have multiple Node processes, sure. But how > do I serialize/synchronize these processes when doing a set of (non-atomic) > operations in an atomic manner over, say, a filesystem or a database? > > Locking! Filesystem locks provided by your OS, or a distributed lock > service. A proper distributed lock service lets you scale across machines, > not just CPUs, of course. > > And then if you can design things to be stateless or use data types like > CRDTs, you may be able to avoid locking for some tasks. >
Afterthought: It will be nice if Node can support a distributed lock service out of the box thereby making its cluster feature "more complete". Meaning, if I can spawn, fork etc from within Node, then I should also be able to coordinate the work of these new processes using Node JS API itself. -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/2a30b9b4-2c3f-4dfd-a933-cb866162a3f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
