Boomi vs. IBM MQ

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

Suited:

• As we have critical data such as payments which needs to be managed across a number of platforms.
• MQ ensures guaranteed delivery of this data.
• Setting up a new application to use MQ is a relatively simple process.
• To track data both internally and externally you can set MQ up to send back acknowledgement . Very useful if one party say they have not received some data.

Not suited.

• If an application has a requirement to get information from a database without any concerns of losing data . Using JDBC connecting directly to the database can reduces the number of jumps the application needs to make to get to the database.

• If an application wants to store information and then send as a large batch file it is not recommended to use MQ. MQ applications should be used for data which needs to be sent immediately. MFT (MQ file transfer) however can utilise MQ for file transfers

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

• The documentation is very clear,It is understandable and the support helps to configure it in the best way.
• Server guidelines make it possible to get the most out of work management. It's broad, we can work with different operating systems, I really recommend using linux.
• It is highly compatible with systems, brockers, applications, and data accumulation programs, it is possible to configure everything so that after the installation of programs, they can communicate with each other and then throw data to an external program that accumulates it and represents in clear details of steps to follow and make business decisions.

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

• I can only speak wonders about the program; I think it is a program with enough serious track record to meet the company's expectations. However, it should be noted that I could suggest that promotional packages be made from time to time for those of us who are already clients of more than one year.
• In every sense, the program fulfills what it promises, which is to generate a good connection and cohesion of programs to be able to make commitments between them.

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

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 give it a nine because it has significantly improved my team's data reliability and operational efficiency. Its great security features give us peace of mind, knowing our sensitive data is well protected. While the setup might initially be complex, I believe the long-term benefits far outweigh this hurdle.

Incentivized

As I have said before, the program is stable; I think that is the great reason why it has been maintained for years and days in the company; despite the hard use that we have given it, it has behaved well during both day and night shifts.

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

The IBM Support team has offered unmatched insight. Their personnel helped us actualize several things that seemed impossible before. You see, previously we would develop a software solution, but it would take months before rolling it out mostly because we had further build additional specific interfaces. The support team suggested we procure App Connect alongside MQ. Right now, we just hop into the IBM MQ platform, connect the software with AppConnect, and a few modifications are done, then it's ready within a few days.

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.

Kafka is renowned for its impressive throughput, fault tolerance, and real-time data streaming capabilities. Nonetheless, IBM MQ remains the preferred choice due to its unwavering commitment to guaranteed delivery and exceptional reliability. Fault-Tolerant Architectures of IBM MQ which allows active-standby queue managers, to build fault-tolerant architectures that ensure continuity of service in the event of hardware or software failures.

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

• Positive- Message Reliability and Reduced downtime, increases the ROI many times.
• Positive- Increased stability and enhanced customer experience
• Negative- cost is very high - Both licensing and integration cost
• Negative- Learning and training cost of IBM MQ is high as its complex to use and integrate

Incentivized