Boomi vs. Mashery (now part of Boomi)

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

TIBCO Cloud Mashery allows you to quickly enable API access control and management together with quick and easy setup of the developer portal. It focuses on core API management with limited integration features (filters, adapters, orchestration) - so TIBCO Cloud Mashery is mostly suited in a setup which already addresses integration features with other products.

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

• Throttling of requests helps prevent DOS attacks. Attackers try to wreak havoc wherever they can. Mashery helps you control your environments to throttle every endpoint independently.
• The interface for setting endpoints is very intuitive and makes real-time adjustment easy to do.
• TIBCO Cloud Mashery support is superb. I do not have to go to their website to know of any issues. They are proactive in communicating with their customers

Incentivized

• 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

• Mashery should allow orchestration and transformation out of the box rather than it being a service or having to buy additional services.
• The dashboard is easy to use but I think it needs a face lift and it needs to start using TIBCO Spotfire to make it more of a analytical engine.

Incentivized

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

Ease of use.

Incentivized

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

i find some of the package adding and key are complex . UI experience is bad . Every step need front and backward navigation too much. It would be better if endpoint itself contain package and key addiction option

Incentivized

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

Support has been good overall.

Incentivized

Initially it was difficult to understand . after few day , it was easy

Incentivized

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.

Our selection process happened in 2016. TIBCO Mashery's easy hybrid deployment model was the reason why we decided on Mashery over Apigee. Akamai API Gateway is now a new tool on the market evolving really fast but was not available yet when we went through the selection process. Tyk is open source and evolving very fast, but 2 years back, it was not mature enough. That might have changed now.

Incentivized

• 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

• Mashery enabled us to go to market quicker because we didn't have to write systems for authentication and security for ourselves.
• Mashery helps our MTTR when we have issues because we can use their transaction logs to identify and troubleshoot issues.

Incentivized