From: "Adrian Crum" <[email protected]>
Adam Heath wrote:
So each entity creation itself was a separate work unit. Once an
entity was created, you could submit the primary key creation as well.
That's simple enough to implement(in theory, anyways). This design
is starting to go towards the Sandstorm(1) approach.
I just looked at that site briefly. You're right - my thinking was a lot
like that. Split up the work with queues - in other words, use the
provider/consumer pattern.
If I was designing a product like OFBiz, I would have JMS at the front
end. Each request gets packaged up into a JMS message and submitted to a
queue. Different tasks respond to the queued messages. The last task is
writing the response. The app server's request thread returns almost
immediately. Each queue/task could be optimized.
This makes remind me that it's mostly what is used underneath in something like
ServiceMix or Mule (ESBs).
ServiceMix is Based on the JBI concept
http://servicemix.apache.org/what-is-jbi.html
and uses http://activemq.apache.org/ underneath
Jacques
