MuleSoft – Today’s Most used Opensource Enterprise Service Bus

Mule ESB runtime is light weight java based Enterprise Service Bus, which can be integrated between different platforms and languages that can connect fast and communicate between each other.Mule ESB can be deployed anywhere and can orchestrate real time events.

Mule ESB has got below capabilities.

Service creation and hosting — expose and host reusable services, using the 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

Note: Image directly taken from https://www.mulesoft.com/resources/esb/what-mule-esb

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 VP of Product Strategy Ross Mason: To ESB or not to ESB.

1. Are you integrating 3 or more applications/services?
2. Will you need to plug in more applications in the future?
3. Do you need to use more than one type of communication protocol?
4. Do you need message routing capabilities such as forking and aggregating message flows, or content-based routing?
5. Do you need to publish services for consumption by other applications?

Why Mule?

Mule is lightweight but highly scalable, allowing you to start small and connect more applications over time. The ESB manages all the interactions between applications and components transparently, regardless of whether they exist in the same virtual machine or over the Internet, and regardless of the underlying transport protocol used.

There are currently several commercial ESB implementations on the market. However, many of these provide limited functionality or are built on top of an existing application server or messaging server, locking you into that specific vendor. Mule is vendor-neutral, so different vendor implementations can plug in to it. You are never locked in to a specific vendor when you use Mule.

Note: the above two paras are directly taken from Mule website because i feel thats most apt content than i can describe.

In the next comming blog posts i will teach you how to start with mulesoft ESB.
Happy Mule 🙂

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s