MuleSoft vs Dell Boomi
Introduction:
An Integration Platform is software that integrates different
applications and their services. It is a set of automated tools that
integrate software applications that are deployed in different environments.
Dell Boomi
Dell Boomi Atmosphere is an on-demand multi-tenant cloud integration platform for connecting cloud and on-premises applications and data. It enables customers to design cloud integration processes called Atoms and transfers data between cloud and on-premises applications. Boomi provides an integration platform as a service (iPaas), which enables the connection of applications and data services. It is a low-code development platform. The platform provides API, lifecycle management, and event-driven architecture features for cloud integration. Boomi is well suited for integrating ERP systems such as NetSuite, SAP, Salesforce. As a developer here is the neat thing about Boomi - all the certifications provided by Boomi are free.
Reference: https://train.boomi.com/
MuleSoft
MuleSoft is a data integration platform built to connect a variety of data sources and applications and perform analytics and ETL processes. Mule is a runtime engine of Anypoint Platform, are a lightweight Java-based enterprise service bus (ESB) and integration platform that allows developers to connect applications easily and enables them to exchange data.
Reference: https://training.mulesoft.com/
MuleSoft vs Dell Boomi
To better understand both offerings let us dig
deeper into both these compelling offerings.
|
Feature |
MuleSoft |
Dell Boomi |
|
Framework |
MuleSoft is an API-led network. It can connect across multiple
apps and business units |
Boomi
is used in the traditional ETL Middleware approach |
|
Capability |
On-premise, cloud, and hybrid of each |
Cloud and on-premise integration solutions only |
|
Connectors: Data Sources and
Destinations |
Supports around 300 connectors |
Supports application and technology connectors. There are 80
application connectors and 22 technology connectors |
|
API-Management |
API
Manager |
Real-Time
Dashboard |
|
Development Tools |
Anypoint Studio, Anypoint Connectors, Anypoint
Design Center, Anypoint Exchange, and Anypoint Management Center |
Application/Data
Integration, API Management, B2B/EDI Management, Master Data Management,
Flow Management |
|
Transformations/Mappings |
Handles process executions through processors. |
Handles process executions through procedures it calls shapes |
Difference
Between MuleSoft Component’s and Dell Boomi Shap’s:
|
MuleSoft |
Dell Boomi |
||
|
Listener |
Its request data is used
to trigger the flow. You can choose what
methods the source accepts, such as GET, POST or a list of methods, and on
which path to accept requests, thereby allowing the routing of requests
through different flows. |
Start Shape |
This is the main shape that begins the process flow. there are multiple
configuration options available: 1.
Connector 2.
Trading Partner 3.
Data Passthrough 4.
No Data
|
|
Transform
Message |
The Transform Message component
converts input data to a new output structure or format. Ø
Using Drag-and-Drop Mappings between these two trees
are represented by lines that connect input to output fields. Ø
Data weave Language · Map · Map Object · Filter · OrderBy · Pluck etc.. |
Map shape |
Use maps to transform data
from one format to another, or more specifically, from one profile to
another. |
|
Map-Function shape |
you may want to convert a
character to uppercase, change the format of a date or look up a value in a
database. There are two main types
of functions: 1. Standard 2.
User-Defined In Custom Scripting: we have to write in 1.Java
Script 2.Groovy
|
||
|
Choice
Router |
The Choice router
dynamically routes messages through a flow according to a set of DataWeave
expressions that evaluate message content. |
Route shape |
The Route shape conditionally sends documents
through different execution paths based on the value of a specified field. |
|
Scatter-Gather |
The Scatter-Gather
component is a routing event processor that processes a Mule event through
different parallel processing routes that contain different event processors. |
Branch shape |
The Branch shape is used when
you have several actions that you want to execute in sequence. Each branch
consists of a separate path that is executed in sequential
order. ·
Here we can use branches up to 2 to 25 |
|
Sub
Flow |
Sub Flow doesn’t have Source and process it will work on same app. ·
No Error handling and Exception handling. |
Process call shape |
The Process Call shape
enables you to execute another process from within a process. The subprocess
that is called is considered a separate, distinct process execution. |
|
Try Cache |
The Try scope enables
you to handle errors that may occur when attempting to execute any of the
components inside the Try scope. |
Try/Catch
shape |
The Try/Catch shape
captures process-level errors or document-level errors for one or more
documents that fail during an execution. |
|
Error
Handling |
Mule throws a system
error when an exception occurs at the system level and no Mule event is
involved. Ø During application startup. Ø When a connection to an external system
fails. Types: 1. Error
Handler 2. On
Error Continue 3. On
Error Propagate 4. Raise
Error |
Error Handling |
Boomi throws a system
error when an exception occurs at the system level and no Boomi event is
involved. Types: 1. Process
Error 2. Document
Error 3. Atom
Runtime Error |
|
Batch
Processing |
Batch to process each message in the array/collection in the
concurrent/ parallel order. Batch has three phases in Mule: 1.Load And Dispatch 2. Process 3. On Complete |
Flow Control shape |
The Flow Control shape
contains a set of options that allow you to configure how documents are processed
within a process execution. |
|
Parse
Template |
Template is defined as
text with embedded Mule expressions that are evaluated and replaced with
their result. ·
Using HTML |
Message shape |
The Message shape generates a free-flow text message
from a dynamic or static set of input parameters. ·
Using HTML |
|
Flow
Reference |
It’s used to call
another Flow’s |
process call shape |
It’s used to call
another Flow’s |
|
Scheduler |
The Scheduler component
enables you to trigger a flow when a time-based condition is met. 1.Fixed Frequency 2. Cron expression |
|
After building and
deploying a process, you can schedule it to run automatically. |
|
Metadata |
The Transform component
accepts input and output metadata for the message payload, a variable or an
attribute. Like Schema CSV, JSON, XML etc. |
Profile |
Using Profile accepts input and output profile for payload, variable
or an attribute. Like CSV, JSON, XML etc. |
You are able to read more about the published Gartner Group survey
results here.
Conclusion
Both Boomi and MuleSoft have great pedigrees; however, Mulesoft has an edge in modern architecture patterns. I also
appreciate that MuleSoft’s future with Salesforce is well understood; however, Boomi’s recent
acquisition by a private equity firm creates a certain amount of uncertainty
and angst.
References
1. https://searchcloudcomputing.techtarget.com/definition/iPaaS-integration-platform-as-a
service
2. https://www.gartner.com/doc/reprints?id=1-1Z8X5WJH&ct=200615&st=sb
3. https://www.gartner.com/doc/reprints?id=1-247SMI7U&ct=200922&st=sb
4. https://train.boomi.com/
5. https://training.mulesoft.com/

Interesting, It’s important to first understand that MuleSoft and Boomi are built on entirely different frameworks. MuleSoft is an API-led network, this means it uses APIs to communicate. On the other hand, Boomi is frequently used in a traditional ETL middleware approach.
ReplyDeleteThank you for sharing such a nice and interesting blog with us.
ReplyDeleteMulesoft Online Course
Mule ESB Training