Need advice about which tool to choose?Ask the StackShare community!
Amazon SQS vs Samza: What are the differences?
What is Amazon SQS? Fully managed message queuing service. 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.
What is Samza? A distributed stream processing framework. Samza allows you to build stateful applications that process data in real-time from multiple sources including Apache Kafka.
Amazon SQS and Samza can be categorized as "Message Queue" tools.
Some of the features offered by Amazon SQS are:
- A queue can be created in any region.
- The message payload can contain up to 256KB of text in any format. Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests.
- Messages can be sent, received or deleted in batches of up to 10 messages or 256KB. Batches cost the same amount as single messages, meaning SQS can be even more cost effective for customers that use batching.
On the other hand, Samza provides the following key features:
- HIGH PERFORMANCE
- HORIZONTALLY SCALABLE
- EASY TO OPERATE
Samza is an open source tool with 565 GitHub stars and 243 GitHub forks. Here's a link to Samza's open source repository on GitHub.
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 Samza
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 Samza
Sign up to add or upvote consMake informed product decisions
What is Amazon SQS?
What is Samza?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Samza?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Amazon SQS?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+47
+30+26
+23+37+25