Need advice about which tool to choose?Ask the StackShare community!
Amazon SQS vs ZeroMQ: What are the differences?
Amazon SQS (Simple Queue Service) and ZeroMQ are two messaging systems used to facilitate communication between applications. Here are the key differences between Amazon SQS and ZeroMQ:
Messaging Paradigm: Amazon SQS is a fully managed message queuing service provided by Amazon Web Services (AWS). It follows a message queue model, where messages are sent to and received from a queue. It ensures reliable and scalable message delivery and supports both FIFO (First-In-First-Out) and Standard queues. ZeroMQ, on the other hand, is a lightweight messaging library that follows a socket-based messaging paradigm. It provides a set of socket-like APIs that allow applications to send and receive messages directly between each other.
Architecture and Deployment: Amazon SQS is a cloud-based service that is hosted and managed by AWS. It is designed to be highly available, durable, and scalable, making it suitable for distributed applications and microservices in the cloud. In contrast, ZeroMQ is a library that is integrated directly into applications. It is a low-level tool that allows developers to implement messaging patterns directly in their code. ZeroMQ can be used in various deployment scenarios, from local applications to distributed systems.
Message Persistence and Durability: Amazon SQS guarantees message persistence, meaning messages are stored even if the consumer application is not currently available. This ensures that no messages are lost, and the messages can be processed at a later time. ZeroMQ, by default, does not provide built-in message persistence. If a message cannot be delivered immediately, it is discarded. However, developers can implement their own message persistence mechanisms using ZeroMQ's building blocks.
Scalability and Throughput: Amazon SQS is designed for high scalability and can handle a large number of messages and consumers simultaneously. It automatically scales based on demand. ZeroMQ is lightweight and designed for low-latency communication within a single application or across a small set of interconnected applications. It can handle moderate message throughput.
Protocol and Features: Amazon SQS provides a web service API, making it accessible to applications through HTTP or HTTPS protocols. It offers features like message filtering, dead-letter queues, and message attributes. ZeroMQ, being a library, can be integrated into applications using various language-specific bindings and supports a wide range of messaging patterns, including pub-sub, request-reply, and dealer-router patterns.
In summary, Amazon SQS is a fully managed, cloud-based message queuing service that provides high availability, scalability, and message durability, while ZeroMQ is a lightweight messaging library that allows direct communication between applications within a single environment or across a limited network.
Hi! I am creating a scraping system in Django, which involves long running tasks between 1 minute & 1 Day. As I am new to Message Brokers and Task Queues, I need advice on which architecture to use for my system. ( Amazon SQS, RabbitMQ, or Celery). The system should be autoscalable using Kubernetes(K8) based on the number of pending tasks in the queue.
Hello, i highly recommend Apache Kafka, to me it's the best. You can deploy it in cluster mode inside K8S, thus you can have a Highly available system (also auto scalable).
Good luck
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
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.
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.
I want to schedule a message. Amazon SQS provides a delay of 15 minutes, but I want it in some hours.
Example: Let's say a Message1 is consumed by a consumer A but somehow it failed inside the consumer. I would want to put it in a queue and retry after 4hrs. Can I do this in Amazon MQ? I have seen in some Amazon MQ videos saying scheduling messages can be done. But, I'm not sure how.
Mithiridi, I believe you are talking about two different things. 1. If you need to process messages with delays of more 15m or at specific times, it's not a good idea to use queues, independently of tool SQM, Rabbit or Amazon MQ. you should considerer another approach using a scheduled job. 2. For dead queues and policy retries RabbitMQ, for example, doesn't support your use case. https://medium.com/@kiennguyen88/rabbitmq-delay-retry-schedule-with-dead-letter-exchange-31fb25a440fc I'm not sure if that is possible SNS/SQS support, they have a maximum delay for delivery (maxDelayTarget) in seconds but it's not clear the number. You can check this out: https://docs.aws.amazon.com/sns/latest/dg/sns-message-delivery-retries.html
Pros of Amazon SQS
- Easy to use, reliable62
- Low cost40
- Simple28
- Doesn't need to maintain it14
- It is Serverless8
- Has a max message size (currently 256K)4
- Triggers Lambda3
- Easy to configure with Terraform3
- Delayed delivery upto 15 mins only3
- Delayed delivery upto 12 hours3
- JMS compliant1
- Support for retry and dead letter queue1
- D1
Pros of ZeroMQ
- Fast23
- Lightweight20
- Transport agnostic11
- No broker required7
- Low level APIs are in C4
- Low latency4
- Open source1
- Publish-Subscribe1
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon SQS
- Has a max message size (currently 256K)2
- Proprietary2
- Difficult to configure2
- Has a maximum 15 minutes of delayed messages only1
Cons of ZeroMQ
- No message durability5
- Not a very reliable system - message delivery wise3
- M x N problem with M producers and N consumers1
Sign up to add or upvote consMake informed product decisions
What is Amazon SQS?
What is ZeroMQ?
Need advice about which tool to choose?Ask the StackShare community!
What companies use ZeroMQ?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Amazon SQS?
What tools integrate with ZeroMQ?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+47
+30+26
+23+37+25