David

Geert,

Sounds like you have done some work in the worklfow area with Terracotta. I wanted to point out that the platform we’re developing is more than just workflow. I have not checked out your site, but will because we have not yet settled on the workflow engine to be used within our platform.

All,

Now for the shameless sales job:

We are trying to solve several “recurring problems” in our domain, which I think are applicable to many applications (being developers, we are inherently lazy and don’t like writing the same software twice):

1. Integration…with anything (thus Mule)
2. High-volume transactions, upwards of hundreds of millions a day and complex algorithm processing…thus Grid Computing
3. Workflow/BPM
4. Business Rules to drive the end-to-end processing
5. Real-time analytics to statistically analyze any or all of the hundreds of millions of messages in the system
6. Configuration – all of the above are to be configurations and not code to reduce cost of ownership
7. Commodity hardware. e.g. the Google model of having one enormous farm of really cheap computers that are self-aware, discovered, assimilated, provisioned and begin working on application logic.

Out of the above, we have about 40% put together already. Thus the consideration for Open Sourcing the project. I’m interested in any other thoughts anyone may have.

Mike

The company is just using standard java.util queues, which are clustered via Terracotta. They are using ActiveMQ as a way to feed their Mule instance with messages I believe, but that that’s not used in the grid servers.

Nice post

I’m trying to put mule clustered with terracotta, because queues in database are dam slow :)

Can you share some information ?

you made a queue implementation, or you use activemq ?

Cumps