The Mule ESB has an amusing stat line that reads: “103,000+ developers use Mule 3,200 Companies in Production 0 Headaches”
I don’t know if I believe the headache stat but if the other two are even approximately correct, this sounds like a place to be pushing topic maps.
To get the flavor of the community:
From “What is Mule ESB?”
What is Mule ESB?
Mule ESB is a lightweight Java-based enterprise service bus (ESB) and integration platform that allows developers to connect applications together quickly and easily, enabling them to exchange data. Mule ESB enables easy integration of existing systems, regardless of the different technologies that the applications use, including JMS, Web Services, JDBC, HTTP, and more.
The key advantage of an ESB is that it allows different applications to communicate with each other by acting as a transit system for carrying data between applications within your enterprise or across the Internet. Mule ESB includes powerful capabilities that include:
- Service creation and hosting — expose and host reusable services, using Mule ESB as a lightweight service container
- Service mediation — shield services from message formats and protocols, separate business logic from messaging, and enable location-independent service calls
- Message routing — route, filter, aggregate, and re-sequence messages based on content and rules
- Data transformation — exchange data across varying formats and transport protocols
Do I need an ESB?
Mule and other ESBs offer real value in scenarios where there are at least a few integration points or at least 3 applications to integrate. They are also well suited to scenarios where loose coupling, scalability and robustness are required.
Below is a quick ESB selection checklist. To read a much more comprehensive take on when to select an ESB, read this article written by MuleSoft founder and CTO Ross Mason: To ESB or not to ESB.
- Are you integrating 3 or more applications/services?
- Will you need to plug in more applications in the future?
- Do you need to use more than one type of communication protocol?
- Do you need message routing capabilities such as forking and aggregating message flows, or content-based routing?
- Do you need to publish services for consumption by other applications?
I am exploring the Mule site and entries for data integration in particular for those that may be of interest to topic mappers. More anon.