Make (formerly Integromat) automates integration between applications. It features data transformation capabilities within a no-code graphic interface.
The former Integromat was acquired by Celonis in 2020, and the current product Make is a Celonis brand.
$9
per month
Google Cloud Pub/Sub
Score 9.2 out of 10
N/A
Google offers Cloud Pub/Sub, a managed message oriented middleware supporting many-to-many asynchronous messaging between applications.
Integromat is the best tool for business automation in my opinion because unlike Zapier it allows us to integrate with any API even if the app is not available which allows us to create automation even with the less known apps that we use or the ones that we built internally for our own company.
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.
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
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.
Make's easy to understand user interface helps you to visualize what's happening at all times. Could use some tweaks around the navigation from a scenario specifically in the folders and back navigations. I can't tell you the amount of time wasted in that area. When you branch, you can't bring a branch back together in the same scenario which is kind of a bummer as well.
It has many libraries in many languages, google provides either good guides or they're AI generated code libraries that are easy to understand. It has very good observability too.
The pricing schema is very attractive, almost 50% lower than the competition. You could start from free and then grow. It has a pretty big library of connections to other apps and services, which really helps you when everything is a mess. Integromat has a really easy-to-use interface. You could do almost everything with fewer than 5 clicks. Scenarios (automation steps to complete a routine) have graphics so you can configure them more easily.
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.
Integromat allows us to do everything we used to do on Zapier but it doesn't limit us to only the popular apps, with Integromat we're integrating custom APIs and we get data from different servers through GET requests and it's exactly what we needed and Zapier couldn't provide it.
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.
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.
