Hello. I read a discrete amount of documents regarding ESB's and "why should you need one" but a doubt remains.
My project requires an Event Driven SOA Architecture. I don't have the need to integrate various systems nor to orchestrate complex business processes. My first need is to have a good messaging system for message flow through my "medium-complexity" services, either initiated by explicit requests (typically a web service invocation) or by events generated by client and/or other services. I've understood that ESB like servicemix will defenitely help me to manage services search, invocation, interoperability, messaging ecc... all good things that I need, cause the "platform" i've to develop should be the most flexible, loose coupled, and extensible as possible. My doubt is that, for such purposes, a simpler message routing framework can be enough, so my question is: For such purposes, it's anyway preferrable a complete solution with the complexity drawback, like servicemix, or should I look at other solutions? Thank you very much -- View this message in context: http://www.nabble.com/Do-I-need-ServiceMix-only-for-message-routing--tp21454040p21454040.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
