Need advice about which tool to choose?Ask the StackShare community!

Amazon SQS

1.9K
1.6K
+ 1
165
Resque

109
102
+ 1
9
Add tool

Amazon SQS vs Resque: What are the differences?

Amazon SQS: Fully managed message queuing service. Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use; Resque: A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later. Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.

Amazon SQS and Resque are primarily classified as "Message Queue" and "Background Processing" tools respectively.

"Easy to use, reliable" is the primary reason why developers consider Amazon SQS over the competitors, whereas "Free" was stated as the key factor in picking Resque.

Resque is an open source tool with 8.54K GitHub stars and 1.57K GitHub forks. Here's a link to Resque's open source repository on GitHub.

Medium, Lyft, and Coursera are some of the popular companies that use Amazon SQS, whereas Resque is used by MAK IT, NoRedInk, and Yummypets. Amazon SQS has a broader approval, being mentioned in 384 company stacks & 103 developers stacks; compared to Resque, which is listed in 34 company stacks and 8 developer stacks.

Advice on Amazon SQS and Resque
Pulkit Sapra
Needs advice
on
RabbitMQ
Kubernetes
and
Amazon SQS

Hi! I am creating a scraping system in Django, which involves long running tasks between 1 minute & 1 Day. As I am new to Message Brokers and Task Queues, I need advice on which architecture to use for my system. ( Amazon SQS, RabbitMQ, or Celery). The system should be autoscalable using Kubernetes(K8) based on the number of pending tasks in the queue.

See more
Replies (1)
Anis Zehani
Recommends
Kafka

Hello, i highly recommend Apache Kafka, to me it's the best. You can deploy it in cluster mode inside K8S, thus you can have a Highly available system (also auto scalable).

Good luck

See more
Meili Triantafyllidi
Software engineer at Digital Science · | 5 upvotes · 151.9K views
Needs advice
on
ZeroMQ
RabbitMQ
and
Amazon SQS

Hi, we are in a ZMQ set up in a push/pull pattern, and we currently start to have more traffic and cases that the service is unavailable or stuck. We want to: * Not loose messages in services outages * Safely restart service without losing messages (ZeroMQ seems to need to close the socket in the receiver before restart manually)

Do you have experience with this setup with ZeroMQ? Would you suggest RabbitMQ or Amazon SQS (we are in AWS setup) instead? Something else?

Thank you for your time

See more
Replies (1)
Shishir Pandey
Recommends
RabbitMQ

ZeroMQ is fast but you need to build build reliability yourself. There are a number of patterns described in the zeromq guide. I have used RabbitMQ before which gives lot of functionality out of the box, you can probably use the worker queues example from the tutorial, it can also persists messages in the queue.

I haven't used Amazon SQS before. Another tool you could use is Kafka.

See more
MITHIRIDI PRASANTH
Software Engineer at LightMetrics · | 4 upvotes · 95.7K views
Needs advice
on
Amazon SQS
and
Amazon MQ
in

I want to schedule a message. Amazon SQS provides a delay of 15 minutes, but I want it in some hours.

Example: Let's say a Message1 is consumed by a consumer A but somehow it failed inside the consumer. I would want to put it in a queue and retry after 4hrs. Can I do this in Amazon MQ? I have seen in some Amazon MQ videos saying scheduling messages can be done. But, I'm not sure how.

See more
Replies (1)
Andres Paredes
Lead Senior Software Engineer at InTouch Technology · | 1 upvotes · 72.1K views
Recommends
Amazon SQS

Mithiridi, I believe you are talking about two different things. 1. If you need to process messages with delays of more 15m or at specific times, it's not a good idea to use queues, independently of tool SQM, Rabbit or Amazon MQ. you should considerer another approach using a scheduled job. 2. For dead queues and policy retries RabbitMQ, for example, doesn't support your use case. https://medium.com/@kiennguyen88/rabbitmq-delay-retry-schedule-with-dead-letter-exchange-31fb25a440fc I'm not sure if that is possible SNS/SQS support, they have a maximum delay for delivery (maxDelayTarget) in seconds but it's not clear the number. You can check this out: https://docs.aws.amazon.com/sns/latest/dg/sns-message-delivery-retries.html

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Amazon SQS
Pros of Resque
  • 59
    Easy to use, reliable
  • 39
    Low cost
  • 27
    Simple
  • 13
    Doesn't need to maintain it
  • 8
    It is Serverless
  • 4
    Has a max message size (currently 256K)
  • 3
    Easy to configure with Terraform
  • 3
    Triggers Lambda
  • 3
    Delayed delivery upto 15 mins only
  • 3
    Delayed delivery upto 12 hours
  • 1
    JMS compliant
  • 1
    Support for retry and dead letter queue
  • 1
    D
  • 5
    Free
  • 3
    Scalable
  • 1
    Easy to use on heroku

Sign up to add or upvote prosMake informed product decisions

Cons of Amazon SQS
Cons of Resque
  • 2
    Has a max message size (currently 256K)
  • 2
    Proprietary
  • 2
    Difficult to configure
  • 1
    Has a maximum 15 minutes of delayed messages only
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Amazon SQS?

    Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

    What is Resque?

    Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Amazon SQS?
    What companies use Resque?
    See which teams inside your own company are using Amazon SQS or Resque.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Amazon SQS?
    What tools integrate with Resque?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    +47
    49
    69255
    +30
    25
    15346
    +23
    12
    6351
    +25
    7
    2827
    What are some alternatives to Amazon SQS and Resque?
    Amazon MQ
    Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud.
    Kafka
    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
    Redis
    Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.
    ActiveMQ
    Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
    Amazon SNS
    Amazon Simple Notification Service makes it simple and cost-effective to push to mobile devices such as iPhone, iPad, Android, Kindle Fire, and internet connected smart devices, as well as pushing to other distributed services. Besides pushing cloud notifications directly to mobile devices, SNS can also deliver notifications by SMS text message or email, to Simple Queue Service (SQS) queues, or to any HTTP endpoint.
    See all alternatives