SQS vs RabbitMQ Ask Question

SQS vs RabbitMQ Ask Question

I need to create a queue for processing. The queue itself is relatively low-volume. There might be about 1,000 writes to it per hour. The execution of each task might take about a minute each, and are processed almost as soon as the item is added to the queue.

Is there any reason that I might want to implement RabbitMQ instead of something off-the-shelf like Amazon SQS? What are some reasons why an application would need its own queueing system instead of something like SQS?

ベストアンサー1

Here are a few factors to help you decide which one to go for:

  1. RabbitMQ is FIFO by default. Amazon SQS queues can optionally be set to FIFO.

  2. You can setup your own server with RabbitMQ but not in the case of Amazon SQS so the cost gets involved here.

  3. Setting up your own server will require good knowledge of the subject so that you do not leave any corner untouched. This is not the case with Amazon SQS as it is pretty quick to get started with.

  4. Your own RabbitMQ server means maintenance cost down the line which is not the case with Amazon SQS.

おすすめ記事