Boomi vs. Workato

Dell Boomi is well-suited as a middleware to talk between systems. I am a personal fan of Dell's products and I enjoy this service. Dell Boomi is very easy to use, even to the less technically-inclined user. It is less appropriate to use in one system alone, but users would still find it functional in one system alone because it helps manage the system's metadata and allows that system to be integrated with other systems in the future.

Incentivized

Well Suited

• Business Process Work Flows, File Management, Small/Medium # of Records Queried (<~1000)
• Closing a sales deal in system one kicks off work flows in system two for implementation
• Notification of key events in system one via text, outlook event, etc
• While I note management of two-way integrations needs improvement, it is a strength of Workato and easier to set up here than in any other tool.
• Support for connectors business processes require (Docusign, Dropbox, Outlook, Quick Base, Salesforce, etc)

Needs Improvement -

• Management of two-way integrations. It's often a bit of a struggle to create the appropriate fields in both systems to ensure redundant jobs are not run nor infinite loops created. That said, Workato does provide some documentation to counter this.
• Working with Large Data Sets (1000+)

Incentivized

• Pre-built connectors to almost anything which greatly reduce time to release of your integration needs.
• Easy to use development platform with drag&drop features. Non-technical people could build simple integration processes in no time.
• Great user community where you can get quick help if needed. Boomi people hang around there a lot.

Incentivized

• Workato is very easy to pick up and use. You'll be creating complex recipes within days. The UI, workflow, formulas, and other features are very intuitive.
• Workato is very powerful. The native connectors it has to hundreds of software already, allows users to make substantial automation and integrations, but the HTTP connector makes it seem like it has no boundaries. If you are using software that isn't a native Workato connector but it has an API, you can use their HTTP connector to make calls to and from.
• Workato is always making improvements to its platform. This includes adding more connectors, more features, updating current connectors to be more powerful, or expanding on other tools it offers.

• More from a development perspective. It is always difficult to use the properties features. It takes a while to understand how the data/variables can be used across an integration.
• Dell Boomi should also invest more on API Management and not just seen as a ETL,ESB tool.
• Should roll out features more often based on users reviews.

Incentivized

• Customization has a bit of a learning curve associated with it. Be prepared to expand your programming knowledge for any deep customization, however having the option to customize is critical
• Online training material is out there, but can be a bit cumbersome to read through and retain. More straight-forward online training material would help 10 fold

Dell Boomi has provided us with the ability to connect our campus together using our various existing platforms. There are many supported features and have yet to run into something that we cannot do. Its user interface is very intuitive which would allow users to begin developing fairly easily. There is a myriad of resources available

Incentivized

We need to develop Enterprise Application Integrations and Workato was not designed for this

First of all, as a service (cloud service), we don't need to care about server maintenance any more, no worries about incorrect configurations, about down time. Second, for maintaining, we don't need a large team to do it. And of course, using Dell Boomi instead of manual transaction could help us to avoid people mistake while inputting data or doing transactions.

Incentivized

Due to prebuilt recipes, Workato is easy to learn and use for non-technical users if their use case fits the existing recipes. It is not easy for non-technical users to create, modify, debug or maintain complex integrations that are outside the prebuilt recipes.

I would rate Dell Boomi as highly performant. We have used it for 4+ years and have not had any major issues with availability or speed. We also have not observed performance degradation when connecting it with other software solutions.

Incentivized

Boomi support was responsive and knowledgable, however being a closed cloud service, it doesn't have good community support. We found the learning curve to be steep and there aren't avenues like google, forums, or blogs that provide community driven insight into the product or how to go about designing solutions using the tool

Incentivized

They employ an extremely knowledgeable team of problem solvers. I've never had a disappointing interaction or one that has left me still searching for answers. I know that when I ask for help, they'll partner with me until we find a solution together

Incentivized

We discovered that we could not use Workato for our more complex, large enterprise integrations. It was useful for simple workflows that matched the prebuilt recipes.

MuleSoft and Boomi are built on totally different frameworks. Mulesoft is an API-led network whereas Boomi is an ETL middleware approach. In easy words, Mulesoft can connect to several apps and business units, can create and reuse multiple components. Boomi offers only on-premise and on-cloud integration solutions whereas MuleSoft is capable of providing on-premise, on-cloud as well as hybrid solutions. We can say that MuleSoft is much more flexible and offers multiple integration solutions.

We found Workato to be easier to use, more powerful and more robust than other solutions we tested at the time. It simply does the trick and allowed us to implement all that we needed in all the precise details we needed. It gave us all the power, flexibility and autonomy we needed without bogging us down with unjustified complexity. Workato came through for us and that's why we keep using it after three intense years.

• ROI was flat. Coding directly in apps we were knowledgable in would have been faster, but maintenance higher.
• It brought good process to the integration team that was new, however I wouldn't say it was a huge gain monetarily. It is a valid path out of many paths for integration, but doesn't rule them all.

Incentivized

• Workato is an unusual type of software in that it’s very much middle-wear, which means it’s extra important for stake holders in your company (especially those who won’t be interacting with Workato on a daily basis) to see the ROI that Workato can provide. Typically ROI is in developer time, as well as replacements for other SaaS tools. For our team, we move 2X as fast and need 1/2 the developers, so the ROI is just incredible.