Hi! Author of NoFlo here. This has been sort of a longtime hobby project for me, since I read J. Paul Morrison's FBP book: http://www.jpaulmorrison.com/fbp/#book
The UI side of things is still in very early stages, but the engine itself is quite solid. We've been using it for various Extract-Transform-Load tasks, like report generation, as explained in http://bergie.iki.fi/blog/business_analytics_with_couchdb_an...
At Nemein we also have been using it for routing messages between different message queues. This is useful when you want to apply some business rules on them.
For example, in one of the web apps I've been writing, the ORM sends a message on each I/O operation to a queue. NoFlo listens to the queue and routes the messages to correct "business logic queue". This way the ORM can focus on being an ORM, and our workflows can be kept elsewhere.
Great stuff. Too often people don't give attribution to past projects. More often than not, they ignore them and reinvent them poorly. You are doing a great thing by bringing a time tested idea back.
I'm a big fan of true message passing and will check this out.
The UI side of things is still in very early stages, but the engine itself is quite solid. We've been using it for various Extract-Transform-Load tasks, like report generation, as explained in http://bergie.iki.fi/blog/business_analytics_with_couchdb_an...
At Nemein we also have been using it for routing messages between different message queues. This is useful when you want to apply some business rules on them.
For example, in one of the web apps I've been writing, the ORM sends a message on each I/O operation to a queue. NoFlo listens to the queue and routes the messages to correct "business logic queue". This way the ORM can focus on being an ORM, and our workflows can be kept elsewhere.