Boomi is a cloud-based, on-premise, or hybrid integration platform. It offers a low-code/no-code
interface with the capacity for API and EDI connections for integrating with external organizations and
systems, as well as compliance with data protection regulations.
$550
per month
Kognitio
Score 9.0 out of 10
N/A
WX2 is the data and analytics focused data warehouse appliance solution from UK company Kognitio.
N/A
Pricing
Boomi
Kognitio
Editions & Modules
Boomi
$550
per month
No answers on this topic
Offerings
Pricing Offerings
Boomi
Kognitio
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Boomi
Kognitio
Features
Boomi
Kognitio
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
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.
What I like most is the IN Memory capability it is doing, as we all know RAM is faster than disk. The capability to connect different databases. Beginners should also take note of the Data Disk Management because anytime it could go wrong, you should have experience in dealing with this kind of event.
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.
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
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.
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.
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
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.
The understandable and complete tables and graphs, the cleaning methods and the way of encrypting the data are quite feasible, which does not help to prepare our data, it helps that the data that is thrown as results is separated from each other, the process prior to structuring requires high-level advice and is somewhat time-consuming, there is a risk that they overwrite the data themselves by accident at a later time
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.