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

Amazon SQS

2.2K
2K
+ 1
171
Scheduler API

5
16
+ 1
0
Add tool

Amazon SQS vs Scheduler API: What are the differences?

Introduction

Below are the key differences between Amazon Simple Queue Service (SQS) and Scheduler API.

  1. Scalability and Availability: Amazon SQS is a fully managed message queuing service, designed to provide scalability and high availability. It automatically scales up or down based on the message throughput, ensuring that messages are reliably processed. On the other hand, the Scheduler API is used to schedule and run jobs on a defined schedule, but it does not provide automatic scaling or high availability like SQS.

  2. Message Ordering: SQS guarantees the order in which messages are sent and received within a single message group, making it ideal for applications requiring strict message ordering. However, the Scheduler API does not provide any built-in guarantee for message ordering as it primarily focuses on scheduling and running jobs.

  3. Message Retention: SQS allows you to store messages in a queue for up to 14 days, even if they are not processed immediately. This provides flexibility in handling messages that may take longer to process. In contrast, the Scheduler API does not provide any long-term message storage capability as it is primarily focused on scheduling and running jobs.

  4. Job Scheduling Flexibility: The Scheduler API allows you to specify a cron expression or a rate expression to define the schedule for running jobs. This provides flexibility in defining complex schedules based on time or rate. SQS, on the other hand, does not have built-in job scheduling capabilities as it primarily focuses on message queuing.

  5. Visibility Timeout: SQS provides a visibility timeout feature that allows you to control how long a message remains invisible to other consumers after it has been retrieved from the queue. This ensures that a message is not processed by multiple consumers simultaneously. The Scheduler API does not have a visibility timeout feature as it is primarily focused on job scheduling.

  6. Delay Queue: SQS offers a delay queue feature that allows you to delay the delivery of messages for a specified amount of time. This can be useful in scenarios where you want to introduce a delay between the time a message is sent and when it becomes available for processing. The Scheduler API does not have a built-in delay queue functionality.

In summary, Amazon SQS is a scalable and highly available message queuing service that provides features like message ordering, message retention, and visibility timeout. On the other hand, the Scheduler API is primarily focused on scheduling and running jobs, offering flexibility in defining job schedules using cron or rate expressions.

Advice on Amazon SQS and Scheduler API
MITHIRIDI PRASANTH
Software Engineer at LightMetrics · | 4 upvotes · 270.4K views
Needs advice
on
Amazon MQAmazon MQ
and
Amazon SQSAmazon SQS
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 · 206.8K views
Recommends
on
Amazon SQSAmazon 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Amazon SQS
Pros of Scheduler API
  • 62
    Easy to use, reliable
  • 40
    Low cost
  • 28
    Simple
  • 14
    Doesn't need to maintain it
  • 8
    It is Serverless
  • 4
    Has a max message size (currently 256K)
  • 3
    Triggers Lambda
  • 3
    Easy to configure with Terraform
  • 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
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of Amazon SQS
    Cons of Scheduler API
    • 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

      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 Scheduler API?

      It is a simple API to delay SQS messages. Call our APIs and we'll publish your messages when you need them.

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

      What companies use Amazon SQS?
      What companies use Scheduler API?
        No companies found
        See which teams inside your own company are using Amazon SQS or Scheduler API.
        Sign up for StackShare EnterpriseLearn More

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

        What tools integrate with Amazon SQS?
        What tools integrate with Scheduler API?
          No integrations found

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

          Blog Posts

          GitHubPythonNode.js+47
          54
          72312
          GitHubGitSlack+30
          27
          18322
          GitHubDockerAmazon EC2+23
          12
          6566
          GitHubPythonSlack+25
          7
          3155
          What are some alternatives to Amazon SQS and Scheduler API?
          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), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.
          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