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
Google Cloud Pub/Sub
Score 8.8 out of 10
N/A
Google offers Cloud Pub/Sub, a managed message oriented middleware supporting many-to-many asynchronous messaging between applications.
N/A
Jitterbit
Score 7.0 out of 10
N/A
Jitterbit is a cloud integration technology for cloud, social or mobile apps. It provides accessibility for
non-technical users, including easily creating API’s and data transformation scripts within the
integrations.
Boomi is one of the best integration platforms out there, but it still has its niche. It is suitable for most integration scenarios especially those that doesn't require very high throughput. The runtime could be hosted on-prem and in the cloud or even in a hybrid mode, which …
Evaluated Dell Boomi and Celigo as alternatives prior to purchasing Jitterbit. We went with Jitterbit at that time because we could handle all changes ourselves without any assistance from Jitterbit, and we liked their size and nimbleness. Dell Boomi was too big for us, and …
Jitterbit plays well in the general-purpose integration that can be used to integrate multiple systems and used by different departments within an Enterprise. I see it as a more basic option for Boomi that is less expensive. So if you are looking for something like Boomi, and …
Legacy systems often need to be replaced or integrated with new applications in order to modernize businesses. A strong API strategy that avoids custom coding and third-party programs is essential to enable this integration. Boomi's new-age connectivity and integration solutions ensure safe, secure, and robust integration. In the age of information, businesses are under more pressure than ever to be able to collect and manage large amounts of data. This data comes in from a variety of sources, including personalized devices such as voice assistants and wearable tech. While this data can be immensely valuable to businesses, they often lack the infrastructure necessary to handle it effectively. This can lead to data build-up in databases or silos, and can eventually lead to problems with integration and security.
If you want to stream high volumes of data, be it for ETL streaming or event sourcing, Google Cloud Pub/Sub is your go-to tool. It's easy to learn, easy to observe its metrics and scales with ease without additional configuration so if you have more producers of consumers, all you need to do is to deploy on k8s your solutions so that you can perform autoscaling on your pods to adjust to the data volume. The DLQ is also very transparent and easy to configure. Your code will have no logic whatsoever regarding orchestrating pubsub, you just plug and play. However, if you are not in the Google Cloud Pub/Sub environment, you might have trouble or be most likely unable to use it since I think it's a product of Google Cloud.
This is a great tool for bringing data out of your locked, internal systems and getting it into the cloud. It meshes well with Salesforce and is fairly easy to use, helping the transition from other older, more complex tools into a more modern environment. It has lots of competition in this space and some are better than others, but if your data is straight forward and you know it well, Jitterbit will get the job done. If you are not as close or comfortable with your data and need to do some wildly complex migrations, there might be better packages out there for you.
With a pub/sub architecture the consumer is decoupled in time from the publisher i.e. if the consumer goes down, it can replay any events that occurred during its downtime.
It also allows consumer to throttle and batch incoming data providing much needed flexibility while working with multiple types of data sources
A simple and easy to use UI on cloud console for setup and debugging
It enables event-driven architectures and asynchronous parallel processing, while improving performance, reliability and scalability
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.
Migrating operations from QA to Production work well for initial deployment, however, when migrating an update to an existing job to production, sometimes certain project items are duplicated. This is not the end of the world... the duplicates can be removed, but would be nice if it was not required.
I have not found a way to trap under-the-covers SOAP errors (for example, when a query you are running against Salesforce takes too long). You get a warning error in the operation log that the job only pulled a "partial" file, but it does not fail.
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
It serves all of our purposes in the most transparent way I can imagine, after seeing other message queueing providers, I can only attest to its quality.
I have been evaluating other tools as a continuous improvement practice. I would like something that would be easier to use for a non-technical user. I work for a small organization and have no back-up for Jitterbit if something happens to me. We don't have the technically savvy employees to understand it.
My IT and Finance teams have noted that setting up the tool is a breeze. Dell Boomi has never caused an issue during a system implementation that I am aware of. We are pleased with the tool and recommend others consider it.
It is easy to create Google Cloud Pub/Sub topics from both Web Console and CLI commands.
Google Cloud Pub/Sub supports creation of one or more subscriptions.
By supporting a BigQuery Pub/Sub subscription to automatically write to a BigQuery table it simplifies development by avoiding implementation of a custom micro service for writes to BigQuery.
The atom sphere takes a time to load, when I open a process or when I open a log. One more slow processing is when I import objects from NetSuite.
About the performance of processing, it looks like Boomi takes a time to initialize some things such as connectors before starting the process. This is also performance we have.
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
They have decent documentation, but you need to pay for support. We weren't able to answer all our questions with the documentation and didn't have time to setup support before we needed it so I can't give it a higher rating but I think it tends to be a bit slow unless you're a GCP enterprise support customer.
We decided to go with Dell Boomi because another department in our company was already using the software. We did not research competitor applications to use as our business solution. Dell Boomi was very easy and quick to set up, so once we decided to use Dell Boomi for systems integration, we had it set up and running within a few working days.
Having used Amazon Web Services SNS & SQS I can say that even if the latter may offer more features, Google Cloud Pub/Sub is easier to use. On the other hand, usage of SNS & SQS as well as documentation and troubleshooting is easier with the AWS solution. Since we are not using GCP only for Pub/Sub the choice depends on other variables.
Evaluated Dell Boomi and Celigo as alternatives prior to purchasing Jitterbit. We went with Jitterbit at that time because we could handle all changes ourselves without any assistance from Jitterbit, and we liked their size and nimbleness. Dell Boomi was too big for us, and Celigo at that time did not have a self-service model. Every change had to go through them (although that has since changed). We were not in a position to be able to wait for someone to make changes for us given the rate of change within the business.
You can just plug in consumers at will and it will respond, there's no need for further configuration or introducing new concepts. You have a queue, if it's slow, you plug in more consumers to process more messages: simple as that.
It has allowed us to scale significantly without having to add headcount, specifically those geared towards data entry. We went from a $10m ARR business to $200m ARR business with the same amount of Order Processors and 12x amount of transactions by leveraging Boomi to perform a lot of the work, and then having the Order Processing team to simply review that the transaction was processed successfully.
The time it takes to connect systems has reduced by orders of magnitude. Previously, we would custom-develop connectors between various systems and they would all be managed by different vendors. With Jitterbit speed-to-deploy and the efficiency gained by managing all connections in one dashboard has been the greatest piece of the ROI.
