Azure Service Bus vs. Red Hat Fuse

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

RedHat Jboss Fuse can be used perfectly to solve application integration or microservices implementation at the departmental or enterprise level. The wide quantity of connectors it provides allows any application to be integrated. Specific technical and programming knowledge is required to build the interfaces, therefore it is not so appropriate for those companies that do not have these employee profiles.

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

• Hybrid deployment (on-premise, private or public cloud) deployed on OpenShift.
• More than 200 connectors to connect practically everything.
• Scalability
• Pricing and Support

Incentivized

• 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

• Better UI for drag and drop or no-coding integration.

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

RedHat JBoss Fuse has a strong user community, it's fully opensource and it's easy to license with world-class support. It also has strong integration with AMQP messaging system to bring much more control and visibility over integration patterns, messaging flows, and the overall system topology.

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

• Improve business process outcomes
• Improve process agility
• Reduce integration costs
• Reduces operations and monitoring costs

Incentivized