Hi! Scheduling an SQS message for delayed delivery doesn't exist in AWS. Anything past 15 minutes requires you to build your own scheduler.
To solve this, we've built an API for an SQS task scheduler. Call the API with your delay and message, and it will publish to your queue at the scheduled time. It supports delays up to a year, with production level SLA's. You can see how it works here:
Let me know what you guys think, and if anyone would find this useful!
Interesting but to be honest not sure I would use it. Here is why:
Yes, maybe the api isn't as convenient but then again, with a simple cdk command I can spin the construct above up.
I'm not saying ur idea is bad and looking at some other comments there may be a market for it but I cannot imagine a usecase for me that justifies this service as a dependency in my stack.
Hey, np thanks for the feedback. It's possible to do that, but if you have a lot of messages with long delays, the consumers are mostly passing messages back and forth and not actually consuming anything any more. If a message was delayed 24 hours for example, then that message will have bounced between the two queues almost 100 times.
Can't you just wrap your object in SQS in something that specifies the earliest time it can be published and if it's not past that time...put it back in the queue with the appropriate delay? Why is using, and depending on, a third party service better?
Nice! I use Aws SQS for my projects but don't need longer delay. I'll remember your product in case I need it in the futur.
Thanks man, np and lmk if you do need it in the future!