Select Page

Mule ESB role in IT systems integration architecture


Mule ESB as an integration platform

Mule ESB is an architecture used for application integration. The name – Enterprise Serial Bus – derives from the fact that it performs an analogous function to physical data buses found in computers, but on a higher abstraction level. Applications connect their services to the bus, creating “end points”, while the bus takes over all responsibilities related to routing and message transformation.

Mule Enterprise Service Bus Logo

This means that the application does not have to know anything about the physical location of other services, communication protocols, etc. The bus also makes it possible to perform such functionalities as message transformation and their routing in a way that is transparent to the applications.

The ESB architecture allows for application integration, just like traditional EAI platforms. There is, however, a fundamental difference between them. The ESB bus supports functionalities traditionally offered by the EAI broker – message routing using rules, data transformation, application adapters, etc.

However, in ESB architecture these functionalities can themselves be the elements of the bus, which allows for their dispersion and independent scaling when needed. This makes it possible to deploy only those functionalities that are actually necessary and avoid the necessity of creating more broker instances, with only a small part of their possibilities used.

Shortened “Time to Market”

The solutions implemented on the basis of engine Mule ESB have characteristics of “package”. This means that services can be grouped into projects, in accordance with a logical division of the API (or logic of the system), so phase: implementation, testing and implementation can successfully weave in next project phase. This approach is perfectly compatible concepts of agile methodologies in software development, where systematically are delivered next parts of the system.

Mule ESB integration technology assessment

The Mule ESB solution may easily be called mature due to the fact that it is stable and there is a wide range of available step types (including connectors) of which flows are built. MuleSoft is currently the supplier of a universal IDE called Anypoint Studio, which is based on Eclipse-type tools allowing users to quickly learn what the Mule platform has to offer. With Anypoint Studio, we can build flow definitions using universal elements provided with the solution. What is worth mentioning is that it is also possible to build own elements and install other, previously created ones. This enables the IDE to create and test newly made solutions, which significantly reduces the anticipated solution’s preparation time. Mule ESB is also widely supported, both by MuleSoft and the community.

To date, MuleSoft has been constantly expanding the entire solution by supplying new

versions of Mule ESB and Anypoint Studio, which guarantees high reliability and

congruence with market needs.

Summarizing, with Mule ESB it is possible to:


define process flows,

implement complex logic using the following languages: Java, Ruby, Groovy, Python, JavaScript,
quickly and efficiently build SOAP or REST services,

integrate with the following using ready-for-use connectors:

– databases (object and non-object),

– JMS servers (ActiveMq, WebSphare MQ and the like),

– SOAP- and REST-type services,

– network shares and FTP servers,

– mail servers,

– and the like,


test the solution with unit tests,
generate flow documentation (diagram, configuration),
efficiently transfer the code to the server by exporting directly from Anypoint Studio.

Below screens with Anypoint Studio:

Screen AnypointStudio, Mule ESB
Screen AnypointStudio, Mule ESB

Elastic migration from Community to Enterprise

Mule projects can be run either on the Community and Enterprise runtime engine. If you decide to use the Enterprise version and make use of all its advantages, is not required to
interfere in the previously delivered code. The solution based on open source provides most of the mechanisms needed to implement services and is primarily addressed to companies looking for savings omissions the license fees

BlueSoft experience with Mule ESB

BlueSoft has plenty of experience in building solutions based on Mule ESB in integration and back-end solutions for systems supporting queuing (most common used: WebSphere MQ, Active MQ) and operations on database (Oracle, PostgreSQL, MySQL, MongoDB).

As one of the few companies in Poland, we have successfully completed the following projects using Mule ESB:

– We have designed and implemented a services for a large Polish air carrier using the Amazon cloud.

– We have designed and implemented API for system ICC (Inter Carrier Communication) combining heterogeneous IT systems in a large telecommunications company.

– We have designed and implemented a flexible solution that delivers service layer and the canonical data model for customers in the pharmaceutical industry.

BlueSoft has successfully implemented many projects in this area. We will happily present our portfolio directly as well as answer more questions about technology itself and benefits to be brought by its implementation.

Technology website: MuleSoft

See other technologies, which we use in this area

Integration technologies