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

Celery

1.5K
1.6K
+ 1
279
MQTT

574
548
+ 1
7
Add tool

Celery vs MQTT: What are the differences?

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.

What is MQTT? A machine-to-machine Internet of Things connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.

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

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

Udemy, Sentry, and Postmates are some of the popular companies that use Celery, whereas MQTT is used by Pubu, Jaumo, and Danale Inc. Celery has a broader approval, being mentioned in 272 company stacks & 77 developers stacks; compared to MQTT, which is listed in 12 company stacks and 6 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Celery
Pros of MQTT
  • 98
    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
  • 3
    Varying levels of Quality of Service to fit a range of
  • 2
    Lightweight with a relatively small data footprint
  • 2
    Very easy to configure and use with open source tools

Sign up to add or upvote prosMake informed product decisions

Cons of Celery
Cons of MQTT
  • 4
    Sometimes loses tasks
  • 1
    Depends on broker
  • 1
    Easy to configure in an unsecure manner

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

It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.

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

What companies use Celery?
What companies use MQTT?
See which teams inside your own company are using Celery or MQTT.
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 MQTT?

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

Blog Posts

GitHubPythonNode.js+47
54
71928
JavaScriptGitHubPython+42
53
21348
GitHubPythonSlack+25
7
3091
GitHubPythonDocker+24
13
16956
What are some alternatives to Celery and MQTT?
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