CloudAMQP vs ZeroMQ

Need advice about which tool to choose?Ask the StackShare community!

CloudAMQP

57
72
+ 1
7
ZeroMQ

226
521
+ 1
72
Add tool

CloudAMQP vs ZeroMQ: What are the differences?

What is CloudAMQP? RabbitMQ as a Service. Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms.

What is ZeroMQ? Fast, lightweight messaging library that allows you to design complex communication system without much effort. 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.

CloudAMQP and ZeroMQ belong to "Message Queue" category of the tech stack.

Some of the features offered by CloudAMQP are:

  • 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.

On the other hand, ZeroMQ provides the following key features:

  • Connect your code in any language, on any platform.
  • Carries messages across inproc, IPC, TCP, TPIC, multicast.
  • Smart patterns like pub-sub, push-pull, and router-dealer.

"Some of the best customer support you'll ever find" is the top reason why over 3 developers like CloudAMQP, while over 17 developers mention "Fast" as the leading cause for choosing ZeroMQ.

ZeroMQ is an open source tool with 5.33K GitHub stars and 1.57K GitHub forks. Here's a link to ZeroMQ's open source repository on GitHub.

Binary.com, GrowSumo, and Runbook are some of the popular companies that use ZeroMQ, whereas CloudAMQP is used by Travis CI, Guaana, and Apartment List. ZeroMQ has a broader approval, being mentioned in 35 company stacks & 12 developers stacks; compared to CloudAMQP, which is listed in 12 company stacks and 5 developer stacks.

Advice on CloudAMQP and ZeroMQ
Meili Triantafyllidi
Software engineer at Digital Science · | 6 upvotes · 297K views
Needs advice
on
Amazon SQSAmazon SQSRabbitMQRabbitMQ
and
ZeroMQZeroMQ

Hi, we are in a ZMQ set up in a push/pull pattern, and we currently start to have more traffic and cases that the service is unavailable or stuck. We want to: * Not loose messages in services outages * Safely restart service without losing messages (ZeroMQ seems to need to close the socket in the receiver before restart manually)

Do you have experience with this setup with ZeroMQ? Would you suggest RabbitMQ or Amazon SQS (we are in AWS setup) instead? Something else?

Thank you for your time

See more
Replies (2)
Shishir Pandey
Recommends
RabbitMQRabbitMQ

ZeroMQ is fast but you need to build build reliability yourself. There are a number of patterns described in the zeromq guide. I have used RabbitMQ before which gives lot of functionality out of the box, you can probably use the worker queues example from the tutorial, it can also persists messages in the queue.

I haven't used Amazon SQS before. Another tool you could use is Kafka.

See more
Kevin Deyne
Principal Software Engineer at Accurate Background · | 5 upvotes · 98.7K views
Recommends
RabbitMQRabbitMQ

Both would do the trick, but there are some nuances. We work with both.

From the sound of it, your main focus is "not losing messages". In that case, I would go with RabbitMQ with a high availability policy (ha-mode=all) and a main/retry/error queue pattern.

Push messages to an exchange, which sends them to the main queue. If an error occurs, push the errored out message to the retry exchange, which forwards it to the retry queue. Give the retry queue a x-message-ttl and set the main exchange as a dead-letter-exchange. If your message has been retried several times, push it to the error exchange, where the message can remain until someone has time to look at it.

This is a very useful and resilient pattern that allows you to never lose messages. With the high availability policy, you make sure that if one of your rabbitmq nodes dies, another can take over and messages are already mirrored to it.

This is not really possible with SQS, because SQS is a lot more focused on throughput and scaling. Combined with SNS it can do interesting things like deduplication of messages and such. That said, one thing core to its design is that messages have a maximum retention time. The idea is that a message that has stayed in an SQS queue for a while serves no more purpose after a while, so it gets removed - so as to not block up any listener resources for a long time. You can also set up a DLQ here, but these similarly do not hold onto messages forever. Since you seem to depend on messages surviving at all cost, I would suggest that the scaling/throughput benefit of SQS does not outweigh the difference in approach to messages there.

See more
Decisions about CloudAMQP and ZeroMQ
Mickael Alliel
DevOps Engineer at Rookout · | 4 upvotes · 321.4K views

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!

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of CloudAMQP
Pros of ZeroMQ
  • 4
    Some of the best customer support you'll ever find
  • 3
    Easy to provision
  • 24
    Fast
  • 20
    Lightweight
  • 11
    Transport agnostic
  • 7
    No broker required
  • 4
    Low level APIs are in C
  • 4
    Low latency
  • 1
    Open source
  • 1
    Publish-Subscribe

Sign up to add or upvote prosMake informed product decisions

Cons of CloudAMQP
Cons of ZeroMQ
    Be the first to leave a con
    • 5
      No message durability
    • 3
      Not a very reliable system - message delivery wise
    • 1
      M x N problem with M producers and N consumers

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is CloudAMQP?

    Fully managed, highly available RabbitMQ servers and clusters, on all major compute platforms.

    What is 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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use CloudAMQP?
    What companies use ZeroMQ?
    See which teams inside your own company are using CloudAMQP or ZeroMQ.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with CloudAMQP?
    What tools integrate with ZeroMQ?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    GitHubPythonDocker+24
    13
    16831
    What are some alternatives to CloudAMQP and ZeroMQ?
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    IronMQ
    An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.
    Kafka
    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
    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.
    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.
    See all alternatives