If you don't want to read through the wiki, here's what I've gathered (though I may have misunderstood what they're doing).
This looks like a workflow management system, where you define a dependency graph and their system automatically puts messages in queues, pops them, and executes a step. It seems like it solves the boilerplate part of distributed computing - managing message queues and fault tolerance. Please correct me if I got this wrong or missed something.
Comments
If you don't want to read through the wiki, here's what I've gathered (though I may have misunderstood what they're doing).
This looks like a workflow management system, where you define a dependency graph and their system automatically puts messages in queues, pops them, and executes a step. It seems like it solves the boilerplate part of distributed computing - managing message queues and fault tolerance. Please correct me if I got this wrong or missed something.
Sounds a bit like http://en.wikipedia.org/wiki/Flow-based_programming
I'll have to read through their stuff to see if they have some interesting ideas for my FBP implementation :-)
It does, doesn't it? I still haven't made it through the FBP book, and I'm having a hard time with the author's savior-of-the-world attitude.
Hmm... So you're saying it's a light weight version of Apache Service Mix/Camel? The same way Kestrel is a lightweight implementation of JMS.
"distributed computing boilerplate" ha, I like it