Boomi iPaaS Reviews

We are actually using Boomi in Kubernetes clusters. We deploy it in our own clusters for performance, specifically within the retail industry. Due to the high volumes and numerous integrations, we use Boomi to connect to delivery partners for same-day delivery of products. 

We have a significant number of integrations for our clients, primarily compact with multi-system sources. For example, an order might come from online or through phone. We then determine which delivery partner will handle it, considering they have their own systems. We also monitor the status to see if it has been picked up or delivered.

The maturity of the product is significant. It has been proven in the industry, and we have used it for a long time. When developers learn how to use it, they become productive sooner. 

With Boomi, once your product or order is ready, we connect it with Arbitrate. This helps us choose the delivery partner based on location and price and who can deliver within the necessary time frame.

I have been using Boomi iPaaS, primarily for integration processes involving SAP systems and CRM systems on the cloud, particularly in the pharma industry. I needed to create a connector that could connect these systems, consolidate data into one workflow, and provide an end-user content interface.

Boomi iPaaS has substantially reduced operational costs by providing out-of-the-box connectors that expedite the integration process with enterprise systems. It has also enhanced workflow efficiency by handling errors in data mismatches and has facilitated faster onboarding of new partners in our business network.

We use Boomi for integration. I manage the Boomi team at my company.  

Every product has its pros and cons. Boomi has some drawbacks, but it's generally okay. It could be better in terms of features, flexibility, and especially storage. We have issues there.

In day-to-day operations, tracking transactions is a major challenge. It takes hours to track a single transaction. It is not a straightforward process.

Other products like TIBCO or IBM have simpler transaction tracking by ID. In Boomi, it's much more time-consuming. We need to go through each and every timestamp and identify the transaction details. It is a pain point for us. 

We use Boomi only for process execution. We used it for API and APM but switched to Azure APM. The low latency mode is another pain point. General mode consumes a lot of resources, but to have adequate logging information, we need to deploy in general mode. 

Whereas low latency gives very good throughput and good performance, but we are losing a lot of important information. So these are the some of the aspects. 

Boomi AtomSphere Integration is a product used in some major pharmaceutical companies, making it quite a good solution. I had previously been in a major project where the solution was used. The solution is useful for integration with the data warehouse and SAP systems.

The most valuable feature of the solution is its monitoring part to debug certain issues and find problems.

I use Boomi AtomSphere Integration in my company to manage all types of integrations, including SAP integrations, database integrations, and other enterprise-level integrations.

It allows to migrate to new PaaS services without changing the core of the entrprise  application architecture

The tool's most valuable features I've found are related to debugging and testing. It makes it easy to track execution, documents, and process history. This functionality is particularly useful for identifying issues with data and providing insights to the business.

In my experience, I haven't encountered any major issues with the tool. However, there could be a learning curve for new users, especially depending on which tool you're using. For example, I've used MuleSoft in the past, which is more code-oriented and requires knowledge of Java. Transitioning to Boomi AtomSphere Integration took me a couple of months because of differences in terminology.

One area that could be improved is the CI/CD process. Currently, we use Azure DevOps for CI/CD to deploy Boomi AtomSphere Integration changes to the preferred and productive environments. While it provides deployment scripts, maintaining a comprehensive list of components for deployment can be tedious. There needs to be an easier way to do CI/CD deployment.