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. 

It would be great to have more assistance and credit services for additional features. For instance, virtual class initials are available but not for backend processing moves. Making that more visible, like other Azure products, would be helpful.

Moreover, the documentation is good, but it could be improved. It is changing every day, and I sometimes find that it's not updated enough or some code levels are not included.

I have not been so deeply involved that I could comment on what needs improvement in the solution. In general, I have not been an actual high-level user of the solution to comment on details concerning improvement in the tool.

I remember that one of my customers felt that Boomi AtomSphere Integration was a highly expensive product, owing to which they were looking for cheaper solutions. The high price of the solution is an area of concern where improvements are required.

There are pre-built connectors, but we end up having to create some of them on our own based on API documentation.

Boomi AtomSphere Integration is not yet exposed to the world as a good product owing to certain shortcomings in the area of marketing where improvements are required.

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. 

The tuning for the performance is not great and could be improved.

There are very few string handling functions and few mathematical functions are available.

We'd like technical support to be a little bit better. 

The product could be a little bit more user-friendly.

The company needs to offer better documentation.

The initial setup is complex. It is what it is. You have to deal with it.

There's something missing with Salesforce platform events that they supposedly support, however, it doesn't work well with their cloud platform. It would be nice if they would get that working normally. They say they support it, and yet, it just fires multiple times. It's not reliable. You can't use it. 

It is a costly platform. Its pricing could be better. 

API management and security need improvement. It needs more capability on the API Administration like approval process, automated process, etc.

Lots of enhancements are needed in the API portal so that the developers can view the definitions, try out the APIs, etc.

Many features need to be added to the API analytics, with more drilled down analyses, and also on API security.

Since the application is Java-based, custom scripting within the map data, used to transform shapes to handle more complex process, is lacking in some ways.

There is no validation in the mapping profile custom scripting, such as IntelliSense or advanced error checking.

If one wants to do custom scripts within a map shape, they must have knowledge of Groovy or JavaScript. Only Groovy has the ability to use Java-based libraries.

The scripting capabilities are lacking, in my opinion, based on the user experience. There is not much tooling assistance. There are no “helpers” or examples on how to do more advanced post/pre-processing of data.

For example, if I wanted to parse an XML document using XPath, how would I do that? How do I know the code that I write will compile without having to unit test through trial and error over and over again?

The IDE is lacking in the ability to script. So the biggest benefit of Boomi, being a graphical integration IDE, is a weakness in this sense. Also, you are locked into Groovy as the only language to do advanced scripting.

I’m used to writing code in my preferred IDE, Visual Studio. In VS, there are lots of tools to assist in the writing of scripts (even JavaScript) to have Intellisense and autocomplete help, which cuts down on development time, as well as code quality.

Boomi AtomSphere Integration should scale up on the migration area. 

They have progressed from an ESP architecture, but they have not fully embraced all API design first methodologies. As a result, some features in those areas, such as API management, API gateway, API development, and API dashboards, are missing, but they are still a new product.

Better documentation and more know-how knowledge would be appreciated. When it comes to technical support and designing, they don't have that growth rate.

They are lacking in some streaming features, and messaging features from a listener's point of view.

There should be more scripting possibilities. Boomi is essentially low-code/no-code — it's very graphically oriented. If you wish to maintain it, then you'll require more scripting language.

The product's UI could be more convenient. Its pricing needs improvement as well. They should add a source control feature and provide better integration with Azure DevOps.

AtomSphere Integration would be improved with the addition of a B2B and BPM solution.

Dell is constantly improving because it follows agile development. Every month, Dell keeps adding more and more features.

There are still some areas that need improvement. For example, when updates are going on, the product becomes very slow.

They need to introduce more configurable functions to remove scripting or coding. Scripting should be minimized. It should have exhaustive functions. Currently, it lacks in this aspect.

We would like to see more involvement between Dell Boomi and the end-users to help improve the customer experience.

• There are more mature (dedicated) API management and master data management (MDM) solutions available in the market.
• Dell Boomi does not offer an option for local version control/repositories. (As is also the case usually with other SaaS vendors)
• This may be seen as a disadvantage, but it does not really have any implications other than to rebuild the integrations when moving away from it to a new integration platform. The same holds true when moving away from other integration platforms available in the market.

Boomi consists of several modules, and the API is one product that Boomi is definitely not up to par with. For example, Jitterbit has a better API management module. However, Dell is putting a lot of energy to make changes. There is a new release already now in December or in November (2019), and they're planning some more releases in 2020. But I would say if there is one module that Boomi is less advanced in than the competition it would be the API management. But it might be totally different mid-2020.

Another point that could use improvement for Boomi is license pricing. If you don't know the pricing model very well, you might quickly end up paying more than you expected especially if you are growing and adding integrations. Again, it is different than the competition so it may be difficult to compare, but the pricing model could also clearly be simplified.

It would be helpful if the solution offered some videos for novice settings. Boomi, as a solution, is quite complex for a new user. They need some videos for client implementation for new users. This is needed especially for how users can create connectors and how they can effectively implement the system.

The solution is complex. There's a few items and features that are hard to understand. They should work to simplify the functionality so new users don't struggle.

I haven't found any features lacking, so I'm unsure as to if anything is missing or if anything new could accentuate the current offering.

They should create a custom connector option. With this, they could improve where the user can create the connector, based on their usage.