[LRUG] Amazon Simple Queue Service (SQS)

[Frederick Cheung]

SQS largely takes care of itself. One issue I’ve run into with SQS is that in its default mode reading messages from a nearly empty queue may return no messages (the reason being that the queue is distributed across many machines and reads by default will hit a single partition in the queue, if that one has no messages then the api call will return no message).

You can address this by using the long polling mode - calls to read a message will block up to a configurable limit (upto 20s) before either returning no message or a message that has arrived in the wait period and this mode doesn’t suffer from the limitation I describe. This can either be configured as a setting on the queue or passed as a parameter to individual api calls. If Shoryuken doesn’t support the latter then you might want to set this as a global queue property.

Fred

On 29 May 2015 at 11:31:30, Garry Shutler (garry at robustsoftware.co.uk) wrote:

Hi all,

I'm looking into moving our messaging from Resque to SQS.

I'm looking at using Shoryuken as it seems to be the most mature gem, follows the patterns of Sidekiq, and supports ActiveJob which means we'll be able to switch in Resque/Sidekiq for development as there's no way to run SQS locally.

Do any of you have any "from the trenches" experience you can share around SQS and/or Shoryuken? In particular I've not found much useful stuff on monitoring and administering the queues themselves.

Thanks in advance,
Garry

Garry Shutler
@gshutler
gshutler.com
_______________________________________________  
Chat mailing list  
Chat at lists.lrug.org  
Archives: http://lists.lrug.org/pipermail/chat-lrug.org  
Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org  
List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20150529/1a9eab25/attachment.html>