Hi Hugo, my comments inline:
Use case : - I have high level business processes handled by final users (through Bonita). - A process/task has to be send by Bonita to an ESB (ServiceMix) using ActiveMQ. - Camel gets back the message (the task) and forwards it to an orchestrator (Apache ODE). - The orchestrator has to call all the required webservices of the back ends (for the given task), combine the responses and send it back to Bonita (-> Camel -> ActiveMQ -> Bonita). I have got several questions about this architecture. 1. Are there some misunderstandings of SMX or Apache frameworks in this use-case ?
Why don't you fire directly Camel route from Bonita ? I think that ODE is redondant especially with Bonita.
More over the integration scenarii could be implemented directly with Camel.
2. Does this architecture seem to you well-thought for a high traffic use ?
All depends about your route, the retention that you want, etc. From a general perspective, it should work with a high number of messages.
3. If someboy has already used an similar architecture, do you have any feedback which would be useful for me about come across issues or performance issue or simple advices ?
Yes, we have already implemented such kind of architecture (with Bonita and Talend ESB, but it's possible to do quite the same with ServiceMix).
Regards JB
Thanks in advance ! -- View this message in context: http://servicemix.396122.n5.nabble.com/Question-about-the-coherence-of-an-architecture-using-ServiceMix-4-4-tp5568411p5568411.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
