Need advice about which tool to choose?Ask the StackShare community!
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.
Amazon SQSMithiridi, 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
We offer our customer HIPAA compliant storage. After analyzing the market, we decided to go with Google Storage. The Nodejs API is ok, still not ES6 and can be very confusing to use. For each new customer, we created a different bucket so they can have individual data and not have to worry about data loss. After 1000+ customers we started seeing many problems with the creation of new buckets, with saving or retrieving a new file. Many false positive: the Promise returned ok, but in reality, it failed.
That's why we switched to S3 that just works.
Pros of Amazon S3
- Reliable591
- Scalable492
- Cheap456
- Simple & easy328
- Many sdks83
- Logical29
- Easy Setup12
- 1000+ POPs11
- REST API10
- Secure5
- Easy3
- Web UI for uploading files2
- Plug and play2
- GDPR ready1
- Flexible1
- Faster on response1
- Plug-gable1
- Easy to use1
- Easy integration with CloudFront1
Pros of Amazon SQS
- Easy to use, reliable60
- Low cost39
- Simple27
- Doesn't need to maintain it13
- It is Serverless8
- Has a max message size (currently 256K)4
- Easy to configure with Terraform3
- Triggers Lambda3
- Delayed delivery upto 15 mins only3
- Delayed delivery upto 12 hours3
- JMS compliant1
- Support for retry and dead letter queue1
- D1
Pros of VoltDB
- SQL + Java5
- In-memory database4
- A brainchild of Michael Stonebraker4
- Very Fast3
- NewSQL2
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon S3
- Permissions take some time to get right7
- Takes time/work to organize buckets & folders properly6
- Requires a credit card5
- Complex to set up3
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 VoltDB
Sign up to add or upvote consMake informed product decisions
What is Amazon S3?
What is Amazon SQS?
What is VoltDB?
Need advice about which tool to choose?Ask the StackShare community!
What companies use VoltDB?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Amazon S3?
What tools integrate with Amazon SQS?
What tools integrate with VoltDB?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+5
+5
+7
+6
+4
+4
+17
+4