Our team ran a comparison of IBM’s Integration Bus vs. Mule ESB in order to determine what sort of ESB software was the best fit for our organization. Ultimately we decided to choose IBM Integration Bus to handle our integration needs. This solution approaches application integration from a user-oriented point of view. There is an intuitiveness to this program in that anyone can learn to use the software fairly quickly. Users are enabled to learn and develop applications that fit their needs. For a program so crucial to the functioning of an organization, this factor makes IBM’s Integration Bus incredibly valuable.
Mule ESB is a software solution that allows organizations to connect and integrate applications with relative ease. However, when it comes to the intuitiveness of the product, Mule ESB lacks the ease of use that IBM Integration Bus offers. This takes multiple forms. As far as being able to integrate applications, the ease truly is relative. Troubleshooting is an area where we felt users were not really considered. In order to troubleshoot Mule ESB, an organization will need a dedicated team of experts. The process is complex and requires a great deal of technical knowledge to execute properly. In order to troubleshoot potential issues, either an expert would need to be brought on or employees would have to receive advanced technical training.
IBM Integration Bus handles all of the API language conversions, code conversions, and log maintenance that a company may require. This drastically cuts the time and resources that your organization would need to devote to its projects in order to implement any integration changes to your systems.
As is true with troubleshooting Mule ESB, unless you are someone who has years of experience, integrations can prove to be more challenging than a company might hope for. It is not feasible for just anyone to learn how to use this product, which means that you will need a team of dedicated experts to use it effectively. Mule ESB cannot match the automation that IBM Integration Bus can offer.
Both IBM Integration Bus and Mule ESB are products that aim to aid in the integration of users’ applications. However, IBM’s intuitiveness and automated features make it by far the superior solution.
Senior Principal Architect at Invenio Business Solution Pvt Ltd
12 July 21
I was previously part of the Oracle SOA/OSB development team. In my current capacity I architected solutions using MuleSoft Anypoint Platform on cloud / on-premises and hybrid modes and on PCE/RTF on Self Managed Kubernetes and On-premise apart from regular CloudHub Deployment;
I am presuming you already took the decision of going with MuleSoft; Hence I wouldn't be dwelling on why migration;
I would be considering the following things:
1. ESB to API led connectivity: -- it would be a paradigm shift since its a layered approach w.r.t. the services System/ Process and Experience layers; If you are re-writing the whole stuff at a time that's one way but considering the business continuity that might not be a practical approach.
2. Deployment -- Cloud / On-Premises / Hybrid;
3. What is the type of deployment: Naked Mule / Runtime Fabric / Pure Cloud with CloudHub
4. If on Runtime Fabric -- is it self managed Kubernetes over AWS / Azure / GKE?
5. How are my previous integrations? -- Is it Monolithic? -- You need to consider the Strangler pattern to move -- start migrating few services first and the rest of them later so that you don't lose business continuity.
6. If yes, how do I break it down? -- What are business-critical systems -- how do you take care of them?
7. What is my Database / If I am moving to Microservices
-- how do I take care of a single monolithic database -- What pattern would I be using -- Shared Database per service?
-- If you have multiple data sources how would you take care? -- Like CQRS pattern?
8. Traditional ESB takes care of Transactions -- but in Microservices led world the services would be lightweight and less dependent and have disparate data sources -- you might need SAGA + CQRS patterns based on how are you managing the data.
9. Security: You need to consider based on deployment model and other deployment criteria security at different levels -- Infrastructure level i.e. firewall / Load balance level for DDoS, IP Whitelisting etc.. whereas at the API level you might look at Rate limiting / Client Id etc.. and At the Organization level you might go for SSO / OAuth with JWT tokens.
10. Microservices Architecture requires Message Queues for loose coupling -- on CloudHub you might have Anypoint MQ but in other cases you might need Active MQ or some other mechanism.
11. Batch Processes with Chron Jobs are another issue that you need to take care of. If you don't plan them properly they can eat up your CPU because they need a lot of memory. Since 4.x later streaming is supported -- orchestrate your Batch Jobs carefully
12. Transformations in Dataweave: This is another tricky thing -- if you have all your business logic here it would make your integrations non-portable-
13. Business Rule Engine Integration: -- Mule doesn't come with a BRE integrated so you have to use 3rd party BRE like Drools or Groovy-based Rule engine etc.
14. Work Flows: Mule doesn't have any workflow support that requires human intervention. hence you might look at something like Activity or Flowable or Apache Airflow to integrate a few of your scenarios.
PeerSpot’s crowdsourced user review platform helps technology decision-makers around the world to better connect with peers and other independent experts who provide advice without vendor bias.
Our users have ranked these solutions according to their valuable features, and discuss which features they like most and why.
You can read user reviews for the Top 5 Enterprise Service Bus (ESB) Tools...
Hi community members,
As usual, this new Community Spotlight shares with you the latest articles, questions and trending discussions from your peers.
See what is trending at the moment and chime in to discuss!
Top 8 Extended Detection and Response (XDR) Tools 2022
Would you recommend replacing Cisco ASA Firewall with Fortinet FortiGate FG 100F due to cost reasons?
What is the...