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
CData DBAmp
Score 9.0 out of 10
N/A
DBAmp is a Salesforce integration solution for any SQL DBA. With DBAmp, users can access Salesforce data in real-time using standard SQL. For many organizations, SQL Server plays a critical role in BI and operational reporting. Using DBAmp, users can extend the same SQL Server integrations they've built for BI, analytics, and reporting to Salesforce data.
$2,495
per user
Pricing
Boomi
CData DBAmp
Editions & Modules
Boomi
$550
per month
Single Server License One-year Subscription
$2,495
per user
Offerings
Pricing Offerings
Boomi
CData DBAmp
Free Trial
No
Yes
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
CData DBAmp
Features
Boomi
CData DBAmp
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.
Well suited as an inexpensive tool as "middleware" between your on-prem or hosted SQL Server. Not sure how well it will translate to cloud-based SQL as a platform (Azure SQL) as it relies on linked servers. This tool only applies to Salesforce CRM - not Marketing Cloud. For writing back to Salesforce we did run into Salesforce resource limitations when extensive triggers existed on the objects.
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.
Because it uses Linked Servers, not sure how this will work in Azure SQL.
Replicated tables are based on user security - this means you have to pay for a license to set this up.
There is no built-in function to skip tables or fields on secured tables. This has to be done on the CRM side for fields and we built a function to skip tables in the replication logic.
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.
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.