Hey Norman, I highly recommend Dale's blog series on Actors: http://www.dalnefre.com/wp/ (start with oldest and work your way forward in time). It is well documented with lots of references to interesting writings.
In particular to your comment on "I need a system that can run continuous and can be fault tolerant" you may want to take a look at the Ken protocol: https://www.usenix.org/system/files/conference/atc12/atc12-final206-7-20-12.pdf >From the website (http://ai.eecs.umich.edu/~tpkelly/Ken/): Ken is a lightweight C implementation of a rollback-recovery protocol that > provides crash-restart resilience to distributed applications. Ken unifies > and automates reliability for both application data "at rest" (local > process state) and data "in motion" (messages in a distributed system). Ken > ensures that crash-restart failures (power failures, kernel panics, process > crashes) can't corrupt or destroy data, and Ken guarantees that messages > are reliably delivered and processed by recipients in process-pairwise-FIFO > order. Ken furthermore provides strong global correctness guarantees and > prevents crash-restart failures and packet losses from causing a > distributed system to emit incorrect outputs. Finally, Ken's strong > guarantees compose effortlessly when independently developed Ken-based > distributed systems are integrated. I'm happy to discuss more specifics if you'd like. Cheers, Tristan On Tuesday, September 24, 2013 12:56:39 PM UTC-5, Norman Paniagua wrote: > > Thanks for the resources… > > I read somewhere in this groups that c extensions may slow down nodejs, > and fibers just is written in c++, don't know yet how it may affect the > performance of the app that uses it. > > Regards > > -- > Norman Paniagua > > On Tuesday, September 24, 2013 at 12:32 PM, Matthew Browne wrote: > > If you want to learn more about the actor model, I highly recommend > looking into some resources by its creator, Carl Hewitt. In particular, > check out this video: > > > http://channel9.msdn.com/Shows/Going+Deep/Hewitt-Meijer-and-Szyperski-The-Actor-Model-everything-you-wanted-to-know-but-were-afraid-to-ask > > Here's his original 1976 paper introducing the actor model: > http://dspace.mit.edu/handle/1721.1/6272#files-area > > I still think creating an actor library on top of fibers would work great > for node.js but I haven't had a chance to try it out yet...does anyone else > agree that this is a good idea? > > > On 9/24/13 9:28 AM, Norman Paniagua wrote: > > This concept its new for me, but as far as I read this approach it good to > solve other problems that cannot be solved with the traditional paradigm. > In my case I need a system that can run continuous and can be fault > tolerant, maybe its more memory expensive this approach but in terms of > system stability and zero downtime seem to be good. > > Another think I like its to learn the way that this methodology works, > starting maybe a prototype project. Seems that some people try the same but > seems that their projects are not popular or poorly maintained (I just see > the commits and contributors of each and its to low). > > Someone has experience with those kind of frameworks? (not specifically > using nodejs, can be also with other languages too, I want advices and/or > articles that discuss about this). > > Regards > > PD: I just start reading ACTORS: A Model of Concurrent Computation in > Distributed Systems <http://dspace.mit.edu/handle/1721.1/6952> (free > available at MIT site) > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > 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 post to this group, send email to [email protected] <javascript:> > To unsubscribe from this group, send email to > [email protected] <javascript:> > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to a topic in the > Google Groups "nodejs" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/nodejs/iHSkdmGaRnk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > 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 post to this group, send email to [email protected] <javascript:> > To unsubscribe from this group, send email to > [email protected] <javascript:> > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to a topic in the > Google Groups "nodejs" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/nodejs/iHSkdmGaRnk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
