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
Kaminario K2 (discontinued)
Score 8.0 out of 10
N/A
Kaminario K2 was an on-premise flash array storage. Silk updated its brand and focus to reflect the move of customers to the cloud. The former Kaminario K2 product is no longer available.
N/A
Pricing
Boomi
Kaminario K2 (discontinued)
Editions & Modules
Boomi
$550
per month
No answers on this topic
Offerings
Pricing Offerings
Boomi
Kaminario K2 (discontinued)
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
Kaminario K2 (discontinued)
Features
Boomi
Kaminario K2 (discontinued)
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.
K2 works well in our mixed-use virtual environment. I would not hesitate to place any workload on K2, it has always performed well. We use fiber-channel connectivity as it replaced our large legacy storage array, replacing one rack of spinning disks with 4U of flash.
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.
We performed a bake-off with K2 and one other vendor and they performed identically. K2 pricing was aggressive, performance was great, and it offered the features that we needed at a price that we could afford
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.
