We were asked to find out the best open source ESB to be used for a new product our company is designing.
Step 1
Found the key players we need to evaluate. We looked at industry standard ESB evaluations, latest Forrester and Gartner reports.
The Forrester ESB Evaluation -2011
Gartner Magic Quadrant for SOA Infrastructure Projects - 2012
Short listed candidates,
- Fuse ESB
- Mule ESB
- WSO2 ESB (A Sri Lankan company made it! wow)
Step 2
Decided on evaluation criteria based on the product requirement.
1
|
Support multiple protocols
|
2
|
Dynamic configuration
|
3
|
Dynamic Integration of multiple components
|
4
|
Hot deployment
|
5
|
Retry mechanism
|
6
|
Service pooling
|
7
|
Dynamic content based routing
|
8
|
Flexible service coordination
|
9
|
Expose multiple services as a single service
|
10
|
Web based UI components
|
11
|
Message transformation
|
12
|
Embedding the ESB runtime in a Java application
|
Step 3
Evaluated the short listed products against the criteria.
Evaluation details are bit too lengthy and techi for a simple blog post.
WSO2 ESB which claimed to be great in performance, which was even selected by eBay for their platform (case study available on net), had to be rejected because they did not recommend hot deployment which we really wanted.
FuseESB which scored great against all the evaluation criteria was chosen without much debate. Being based on Apache Camel was a big plus point.
Nice Article. ALL In ONE. Saved time in Google Search
ReplyDeleteIf you looking for more details there are some important features in WSO2 Enterprise Service Bus
ReplyDeleteCan we update this as we are in 2020, please?
ReplyDeleteWhat are free software people who manage their whole IT infrastructure using as a middleware (not SaaS, please) from front ends to micro service REST APIs back ends?