Amazon SQS
Amazon SQS

935
441
125
Celery
Celery

837
494
239
Add tool

Amazon SQS vs Celery: What are the differences?

What is 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.

What is Celery? Distributed task queue. Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS and Celery belong to "Message Queue" category of the tech stack.

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

Celery is an open source tool with 12.7K GitHub stars and 3.3K GitHub forks. Here's a link to Celery's open source repository on GitHub.

According to the StackShare community, Amazon SQS has a broader approval, being mentioned in 381 company stacks & 101 developers stacks; compared to Celery, which is listed in 271 company stacks and 77 developer stacks.

- 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 Celery?

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose Amazon SQS?
Why do developers choose Celery?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using Amazon SQS?
What are the cons of using Celery?
What companies use Amazon SQS?
What companies use Celery?

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

What tools integrate with Amazon SQS?
What tools integrate with Celery?

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

What are some alternatives to Amazon SQS and Celery?
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
Decisions about Amazon SQS and Celery
No stack decisions found
Interest over time
Reviews of Amazon SQS and Celery
No reviews found
How developers use Amazon SQS and Celery
Avatar of Karma
Karma uses Amazon SQSAmazon SQS

In the beginning we thought we wanted to start using something like RabbitMQ or maybe Kafka or maybe ActiveMQ. Back then we only had a few developers and no ops people. That has changed now, but we didn't really look forward to setting up a queuing cluster and making sure that all works.

What we did instead was we looked at what services Amazon offers to see if we can use those to build our own messaging system within those services. That's basically what we did. We wrote some clients in Ruby that can basically do the entire orchestration for us, and we run all our messaging on both SNS and SQS. Basically what you can do in Amazon services is you can use Amazon Simple Notification Service, so SNS, for creating topics and you can use queues to subscribe to these topics. That's basically all you need for a messaging system. You don't have to worry about scalability at all. That's what really appealed to us.

Avatar of Kalibrr
Kalibrr uses CeleryCelery

All of our background jobs (e.g., image resizing, file uploading, email and SMS sending) are done through Celery (using Redis as its broker). Celery's scheduling and retrying features are especially useful for error-prone tasks, such as email and SMS sending.

Avatar of Cloudify
Cloudify uses CeleryCelery

For orchestrating the creation of the correct number of instances, managing errors and retries, and finally managing the deallocation of resources we use RabbitMQ in conjunction with the Celery Project framework, along with a self-developed workflow engine.

Avatar of Brandon Adams
Brandon Adams uses Amazon SQSAmazon SQS

This isn't exactly low-latency (10s to 100s of milliseconds), but it has good throughput and a simple API. There is good reliability, and there is no configuration necessary to get up and running. A hosted queue is important when trying to move fast.

Avatar of MOKA Analytics
MOKA Analytics uses CeleryCelery

We maintain a fork of Celery 3 that adds HTTPS support for Redis brokers. The Winning Model currently uses Celery 3 because Celery 4 dropped support for Windows.

We plan on migrating to Celery 4 once Azure ASE supports Linux apps

Avatar of Simple Merchant
Simple Merchant uses Amazon SQSAmazon SQS

SQS is the bridge between our new Lambda services and our incumbent Rails applications. Extremely easy to use when you're already using other AWS infrastructure.

Avatar of Yaakov Gesher
Yaakov Gesher uses CeleryCelery

We used celery, in combination with RabbitMQ and celery-beat, to run periodic tasks, as well as some user-initiated long-running tasks on the server.

Avatar of Dieter Adriaenssens
Dieter Adriaenssens uses CeleryCelery

Using Celery, the web service creates tasks that are executed by a background worker. Celery uses a RabbitMQ instance as a task queue.

Avatar of Olo
Olo uses Amazon SQSAmazon SQS

Primary message queue. Enqueueing operations revert to a local file-system-based queue when SQS is unavailable.

Avatar of IndiTip
IndiTip uses Amazon SQSAmazon SQS

I can't afford to lose data if Dynamo throttles my writes, so everything goes into a message queue first.

How much does Amazon SQS cost?
How much does Celery cost?
Pricing unavailable