In my mind the short answer is: NO Guillaume Nodet one of the key architects and long time committer on Apache ServiceMix already had his mind set 3 years ago when he wrong this blog post - Thoughts about ServiceMix. That happened in spring , which Guillaume also blogged about. So is all that bad? No its IMHO all great. But that did not happen.
|Published (Last):||15 August 2011|
|PDF File Size:||19.40 Mb|
|ePub File Size:||14.96 Mb|
|Price:||Free* [*Free Regsitration Required]|
In my mind the short answer is: NO Guillaume Nodet one of the key architects and long time committer on Apache ServiceMix already had his mind set 3 years ago when he wrong this blog post - Thoughts about ServiceMix.
That happened in spring , which Guillaume also blogged about. So is all that bad? No its IMHO all great. But that did not happen. ServiceMix did not create a cross product security model, web console, audit and trace tooling, clustering, governance, service registry, and much more that people were looking for in an ESB or related to a SOA suite.
There were only small pieces of it, but never really baked well into the project. That said its not too late. I think the ServiceMix project is dying, but if a lot of people in the community step up, and contribute and work on these things, then it can bring value to some users.
But I seriously doubt this will happen. PS: 6 years ago I was working as a consultant and looked at the next integration platform for a major Danish organization, and we looked at ServiceMix back then and dismissed it due its JBI nature, and the new OSGi based architecture was only just started. That was not the case years ago.
Okay No to ServiceMix - what are my options then? So what should use you instead of ServiceMix? Well in my mind you have at least these two options. These individual projects have regular releases, and you can upgrade as you need. Only legacy users that got on the old ServiceMix 3.
I encourage you to take a read. OSGi is no longer a requirement. IMHO that is very very existing and potentially a changer. I encourage you to check out fabric8 web-site , and also read the overview and motivation sections of the documentation. And then check out some of the videos. After the upcoming JBoss Fuse 6. And users looking for a commercial release can then use JBoss Fuse. Best of both worlds. Summary Okay back to the question - to ServiceMix or not. Then NO. Innovation happens outside ServiceMix, and also more and more outside Apache.
If you have thoughts then you can share those in comments to this blog, or better yet, get involved in the discussion forum at the ServiceMix user forum. PPS: The thoughts on this blog is mine alone, and are not any official words from my employer. Like This Article? Read More From DZone.
Tutorial: Managing Apache ServiceMix clusters with Fuse Fabric
Section 1 About Servicemix 4. Even though there are many open source ESB projects, not all of them are mature enough to be used to solve enterprise mission critical integration problems. ServiceMix is one of the open source projects that is mature enough to be used in these scenarios. ServiceMix, an Apache project, has been around for a couple of years now. It provides all the features you expect from an ESB such as routing, transformation, etc. Section 2 Servicemix 4.
Subscribe to RSS
Getting Started with Apache Camel The Enterprise Integration Patterns EIP book The purpose of a patterns book is not to advocate new techniques that the authors have invented, but rather to document existing best practices within a particular field. By doing this, the authors of a patterns book hope to spread knowledge of best practices and promote a vocabulary for discussing architectural designs. Since the publication of Design Patterns, many other pattern books, of varying quality, have been written. It is common for people to refer to this book by its initials EIP.
How do I use Camel inside ServiceMix?
Getting Started with Apache Camel