Azure Service Bus vs. Make

If you need a cloud-based service bus or a simple to use queue/topic/routing/pub-sub service, then Azure Service Bus is a very good choice at a reasonable price and performance. Typically on-premise we'd use RabbitMQ because it "just works", but if you're building a "cloud-first" application, then this is the one to go with. It's especially easy to integrate with if you're already embedded in the Microsoft ecosystem.

Incentivized

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.

Incentivized

• Acting as a basic queuing service it works very well.
• One of the best parts is that Azure Service Bus can work over HTTPS which helps in strict firewall situations. There is a performance hit if you choose to use HTTPS.
• The routing capabilities are quite good when using topics and subscriptions. You can apply filters using a pseudo-SQL-like language though the correlation filters are quick and easy options.
• Costs are very reasonable at low-ish volumes. If you're processing 10's of millions of messages a month... it may be a different story.

Incentivized

• UI/UX Simplicity and Features
• Workflows are explained in details and even people without IT background can use the tool.
• Consumption is nicely tracked.
• Myriad of existing templates, solutions, and readymade connectors.

• The SqlFilter could be a little easier to use, but it's not terrible.
• The performance while using HTTPS for the connection is a little slow compared to direct connections using AMQP ports.
• There is a size limit to the message - unlike RMQ for instance, Azure Service Bus caps messages to 256kb on the standard tier.

Incentivized

• There are always new platforms and connections that we'd like to see
• More flexibility in paying for operations (tasks) on a sliding scale, instead of by tier
• More thorough support documentation on connecting various platforms and troubleshooting errors

Incentivized

At this point, it is firmly embedded in the DNA of the business and to give up the ability to automate workflows and create integrations on the fly would be a terrible idea.

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.

Incentivized

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.

Incentivized

RabbitMQ is simple and awesome... but so is Azure Service Bus. Both accomplish the same thing but in different environments. If you're building a cloud-native application - especially one that is serverless by design - Azure Service Bus is the only real choice in Azure. It works well, it's performance, and it's reasonably priced in the Standard tier. From our testing, RMQ is more performant, but it's hard to compare service-based implementations vs RMQ installed on VMs.

Incentivized

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.

Incentivized

• Compared to open-source free software like RMQ, Azure Service Bus does have some costs to it. But the cost is reasonable.
• Also unlike RMQ, Azure Service Bus doesn't require you to stand up any hardware - so it's very easy to use and saves time/money from that perspective.

Incentivized

• We used too many credits multiple times and had to buy them additionally, there are no prevention systems to setup to alert before it happens.
• Some consumption is difficult to understand and requires time and digging.
• It requires heavy internal effort to simplify things in Make in order for it to operate cheaper.
• Initial IT setup is paramount and determines a lot.