|
|
|
|
|
by bialecki
5058 days ago
|
|
If you go with SQS, keep in mind it doesn't guarantee that messages will be received exactly once[1]. I've used SQS for large projects and this was killer because we had to implement message locking ourselves to prevent messages from being processed twice. Since then, this has been a deal breaker for using SQS again (now use Celery). [1] http://aws.amazon.com/sqs/faqs/#How_many_times_will_I_receiv... |
|
[1] http://aws.amazon.com/sqs/#functionality