Azure Service Bus vs CloudAMQP

Overview

CloudAMQP

Stacks62

Followers84

Votes7

Azure Service Bus

Stacks553

Followers536

Votes7

Azure Service Bus vs CloudAMQP: What are the differences?

Azure Service Bus and CloudAMQP are both messaging services that provide reliable message delivery between applications. However, there are several key differences between the two platforms.

Pricing Model: Azure Service Bus has a pay-as-you-go pricing model, where customers are charged based on the number of operations performed and the amount of data transferred. On the other hand, CloudAMQP uses a subscription-based pricing model, where customers pay a fixed monthly fee based on the selected plan and the desired features.
Hosting Infrastructure: Azure Service Bus is a fully managed service provided by Microsoft, with the infrastructure hosted on the Azure cloud platform. CloudAMQP, on the other hand, is a hosted RabbitMQ service, where the infrastructure is hosted and managed by CloudAMQP.
Protocol Support: Azure Service Bus supports multiple protocols including AMQP, HTTPS, and Net Messaging. CloudAMQP, being a RabbitMQ-based service, primarily supports the AMQP protocol.
Message Persistence: Azure Service Bus offers reliable message persistence by storing messages in the cloud, ensuring that they are not lost even in the event of failures. CloudAMQP also provides message persistence, but it relies on the underlying RabbitMQ infrastructure for storage.
Integration: Azure Service Bus is tightly integrated with other Azure services, making it easy to integrate with other cloud-based services and applications. CloudAMQP can also be integrated with various cloud platforms and services, but it may require additional configuration and setup.
Scalability: Azure Service Bus provides automatic scaling capabilities, allowing applications to scale up or down based on demand. CloudAMQP also supports scaling, but it may require manual configuration and monitoring to handle increased workload.

In Summary, Azure Service Bus and CloudAMQP differ in terms of pricing model, hosting infrastructure, protocol support, message persistence, integration capabilities, and scalability options.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on CloudAMQP, Azure Service Bus

André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon

.NET Core

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

461k views461k

Comments

Mickael

DevOps Engineer at Rookout

Mar 1, 2020

Decided

In addition to being a lot cheaper, Google Cloud Pub/Sub allowed us to not worry about maintaining any more infrastructure that needed.

We moved from a self-hosted RabbitMQ over to CloudAMQP and decided that since we use GCP anyway, why not try their managed PubSub?

It is one of the better decisions that we made, and we can just focus about building more important stuff!

472k views472k

Comments

Detailed Comparison

CloudAMQP	Azure Service Bus
Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms.	It is a cloud messaging system for connecting apps and devices across public and private clouds. You can depend on it when you need highly-reliable cloud messaging service between applications and services, even when one or more is offline.
Support - 24/7 support, via email, chat and phone.; Real time metrics and alarms - Get notified in advanced when your queues are growing faster than you're consuming them, when you're servers are over loaded etc. and take action before it becomes a problem.; Auto-healing - Our monitoring systems automatically detects and fixes a lot of problems such as kernel bugs, auto-restarts, RabbitMQ/Erlang version upgrades etc.; Metrics - Of course the default RabbitMQ interface is available, which gives you great inspection capabilities of your queues and message throughput, but we also gives you CPU, RAM and disk graphs to help you monitor the health and resource consumption of your clusters.;	-
Statistics
Stacks 62	Stacks 553
Followers 84	Followers 536
Votes 7	Votes 7
Pros & Cons
Pros 4 Some of the best customer support you'll ever find 3 Easy to provision	Pros 4 Easy Integration with .Net 2 Cloud Native 1 Use while high messaging need Cons 1 Observability of messages in the queue is lacking 1 Lacking in JMS support 1 Skills can only be used in Azure - vendor lock-in 1 Limited features in Basic tier
Integrations
AppHarbor Google Compute Engine Heroku DigitalOcean Amazon EC2 Red Hat OpenShift SoftLayer dotCloud Pivotal Web Services (PWS) AppFog	No integrations available

What are some alternatives to CloudAMQP, Azure Service Bus?

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

Related Comparisons

Bootstrap vs Materialize

Django vs Laravel vs Node.js

Bootstrap vs Foundation vs Material UI

Node.js vs Spring-Boot

Flyway vs Liquibase

Azure Service Bus vs CloudAMQP: What are the differences?

Azure Service Bus and CloudAMQP are both messaging services that provide reliable message delivery between applications. However, there are several key differences between the two platforms.

Pricing Model: Azure Service Bus has a pay-as-you-go pricing model, where customers are charged based on the number of operations performed and the amount of data transferred. On the other hand, CloudAMQP uses a subscription-based pricing model, where customers pay a fixed monthly fee based on the selected plan and the desired features.
Hosting Infrastructure: Azure Service Bus is a fully managed service provided by Microsoft, with the infrastructure hosted on the Azure cloud platform. CloudAMQP, on the other hand, is a hosted RabbitMQ service, where the infrastructure is hosted and managed by CloudAMQP.
Protocol Support: Azure Service Bus supports multiple protocols including AMQP, HTTPS, and Net Messaging. CloudAMQP, being a RabbitMQ-based service, primarily supports the AMQP protocol.
Message Persistence: Azure Service Bus offers reliable message persistence by storing messages in the cloud, ensuring that they are not lost even in the event of failures. CloudAMQP also provides message persistence, but it relies on the underlying RabbitMQ infrastructure for storage.
Integration: Azure Service Bus is tightly integrated with other Azure services, making it easy to integrate with other cloud-based services and applications. CloudAMQP can also be integrated with various cloud platforms and services, but it may require additional configuration and setup.
Scalability: Azure Service Bus provides automatic scaling capabilities, allowing applications to scale up or down based on demand. CloudAMQP also supports scaling, but it may require manual configuration and monitoring to handle increased workload.

In Summary, Azure Service Bus and CloudAMQP differ in terms of pricing model, hosting infrastructure, protocol support, message persistence, integration capabilities, and scalability options.