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

Celery

1.6K
1.6K
+ 1
280
Redis

58.1K
44.7K
+ 1
3.9K
Add tool

Celery vs Redis: What are the differences?

Celery is a distributed task queue system while Redis is an in-memory data structure store. Let's explore the key differences between them.

  1. Message Broker vs. Data Store: Celery is essentially a message broker that allows you to manage and distribute tasks across multiple processing units or machines. On the other hand, Redis is primarily a data store that provides fast in-memory storage and retrieval of data.

  2. Task Processing vs. Data Manipulation: Another major difference is the core functionality they provide. Celery is designed to handle the processing of tasks in a distributed manner, where tasks are typically functions or methods that need to be executed asynchronously. Redis, on the other hand, focuses on data manipulation and provides various data structures like strings, lists, sets, and more.

  3. Task Queues vs. Data Structures: Celery utilizes task queues to manage and distribute tasks. It allows you to create queues, prioritize tasks, and distribute them based on availability of workers. In contrast, Redis provides a wide range of data structures like strings, lists, sets, and hashes, which can be used for various purposes including caching, real-time analytics, and more.

  4. Concurrency vs. Persistence: Celery handles task concurrency by allowing multiple workers to process tasks concurrently. It provides a way to scale and distribute tasks across multiple machines. Redis, on the other hand, focuses more on data persistence rather than concurrency. It ensures data durability by allowing you to persist data to disk and provides various mechanisms for replication and fault tolerance.

  5. Task Routing vs. Pub/Sub Messaging: Celery provides flexible task routing mechanisms, allowing you to route tasks to different workers based on predefined rules. It also supports various task result backend options for retrieving the results of completed tasks. Redis, on the other hand, supports publish/subscribe messaging, where you can publish messages to specific channels and subscribers can receive those messages.

  6. Integration with other technologies: Celery integrates well with other technologies and frameworks like Django, Flask, and more. It provides convenient wrappers and utilities for integrating with these frameworks. Redis also has good integration with different programming languages and frameworks, making it easy to use in various application architectures.

In summary, Celery focuses on task processing using task queues and supports task routing and result backends. Redis, on the other hand, is primarily a data store that supports various data structures and provides pub/sub messaging capabilities.

Advice on Celery and Redis
Needs advice
on
CeleryCelery
and
RabbitMQRabbitMQ

I am just a beginner at these two technologies.

Problem statement: I am getting lakh of users from the sequel server for whom I need to create caches in MongoDB by making different REST API requests.

Here these users can be treated as messages. Each REST API request is a task.

I am confused about whether I should go for RabbitMQ alone or Celery.

If I have to go with RabbitMQ, I prefer to use python with Pika module. But the challenge with Pika is, it is not thread-safe. So I am not finding a way to execute a lakh of API requests in parallel using multiple threads using Pika.

If I have to go with Celery, I don't know how I can achieve better scalability in executing these API requests in parallel.

See more
Replies (1)
Recommends
on
rqrqRedisRedis

For large amounts of small tasks and caches I have had good luck with Redis and RQ. I have not personally used celery but I am fairly sure it would scale well, and I have not used RabbitMQ for anything besides communication between services. If you prefer python my suggestions should feel comfortable.

Sorry I do not have a more information

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Celery
Pros of Redis
  • 99
    Task queue
  • 63
    Python integration
  • 40
    Django integration
  • 30
    Scheduled Task
  • 19
    Publish/subsribe
  • 8
    Various backend broker
  • 6
    Easy to use
  • 5
    Great community
  • 5
    Workflow
  • 4
    Free
  • 1
    Dynamic
  • 886
    Performance
  • 542
    Super fast
  • 513
    Ease of use
  • 444
    In-memory cache
  • 324
    Advanced key-value cache
  • 194
    Open source
  • 182
    Easy to deploy
  • 164
    Stable
  • 155
    Free
  • 121
    Fast
  • 42
    High-Performance
  • 40
    High Availability
  • 35
    Data Structures
  • 32
    Very Scalable
  • 24
    Replication
  • 22
    Great community
  • 22
    Pub/Sub
  • 19
    "NoSQL" key-value data store
  • 16
    Hashes
  • 13
    Sets
  • 11
    Sorted Sets
  • 10
    NoSQL
  • 10
    Lists
  • 9
    Async replication
  • 9
    BSD licensed
  • 8
    Bitmaps
  • 8
    Integrates super easy with Sidekiq for Rails background
  • 7
    Keys with a limited time-to-live
  • 7
    Open Source
  • 6
    Lua scripting
  • 6
    Strings
  • 5
    Awesomeness for Free
  • 5
    Hyperloglogs
  • 4
    Transactions
  • 4
    Outstanding performance
  • 4
    Runs server side LUA
  • 4
    LRU eviction of keys
  • 4
    Feature Rich
  • 4
    Written in ANSI C
  • 4
    Networked
  • 3
    Data structure server
  • 3
    Performance & ease of use
  • 2
    Dont save data if no subscribers are found
  • 2
    Automatic failover
  • 2
    Easy to use
  • 2
    Temporarily kept on disk
  • 2
    Scalable
  • 2
    Existing Laravel Integration
  • 2
    Channels concept
  • 2
    Object [key/value] size each 500 MB
  • 2
    Simple

Sign up to add or upvote prosMake informed product decisions

Cons of Celery
Cons of Redis
  • 4
    Sometimes loses tasks
  • 1
    Depends on broker
  • 15
    Cannot query objects directly
  • 3
    No secondary indexes for non-numeric data types
  • 1
    No WAL

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

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.

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

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

Jobs that mention Celery and Redis as a desired skillset
What companies use Celery?
What companies use Redis?
See which teams inside your own company are using Celery or Redis.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Celery?
What tools integrate with Redis?

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

Blog Posts

Nov 20 2019 at 3:38AM

OneSignal

PostgreSQLRedisRuby+8
9
4638
Jun 6 2019 at 5:11PM

AppSignal

RedisRubyKafka+9
15
1638
GitHubDockerReact+17
40
36238
What are some alternatives to Celery and Redis?
RabbitMQ
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Kafka
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
Airflow
Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command lines utilities makes performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress and troubleshoot issues when needed.
Cucumber
Cucumber is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs.
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.
See all alternatives