AUTHOR: http://aws.typepad.com/aws/2011/10/amazon-simple-queue-service-batch-operations-delay-queue-and-message-timers.html LINK!

Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Free Live Stream of AWS GovCloud Summit II | Main | Run Microsoft SQL Server 2012 ("Denali") on AWS Now »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef01539275b0dd970b

Listed below are links to weblogs that reference Amazon Simple Queue Service: Batch Operations, Delay Queue, and Message Timers:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Daniel Bradley

What's the maximum delay on an individual message? The console indicates 15 minutes or would we be able to delay for several days?

Jeffbarr

@Daniel, the maximum delay is 15 minutes. If you need longer delays, please feel free to tell us more about your use case.

Daniel Bradley

@Jeff, thanks for the reply.

To summarise our use case, we use a queue with delays of up to 7 days for delivering news release alerts based on news embargoes. In theory the delay could be any amount, however in practice this is normally just a few days.

We currently use SES for all our immediate alert sending queuing, however, we use a custom MySQL queue for any delayed alerts.

Mike Lewis

15 minutes is definitely way too short, especially since the system can clearly handle much longer delays (ie message retention length).

I'm looking to use message delays to handle user "follow-up" actions several hours after the fact. With only a 15 minute delay available, I'll have to hack a solution by daisy-chaining delays or "failing" messages until they pass a maturity timestamp. Both are pretty ugly compared to a delay value that accommodates a pretty simple (and probably common) problem.

Slegay

+1 for longer delay. Our use case involves outbound notification message re-queuing (where the user endpoint is not responsive). We want to use an increasing delay for each delivery re-try (1st retry after 5 minutes, second retry after 15 minutes, 3rd retry after an hour, 4th retry after a day). Very similar to an email delivery algorithm actually. 15 minutes is way too short.

What was the original use case when you guys decided to build this feature?

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30