Celery: Distributed Task Queue is described as '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' and is an app. There are more than 10 alternatives to Celery: Distributed Task Queue for a variety of platforms, including Windows, Linux, Self-Hosted, Mac and Ruby on Rails apps. The best Celery: Distributed Task Queue alternative is RabbitMQ, which is both free and Open Source. Other great apps like Celery: Distributed Task Queue are Apache Pulsar, Zenaton, ØMQ and sidekiq.
RabbitMQ is a complete and highly reliable enterprise messaging system based on the emerging AMQP standard
Apache Pulsar is a distributed, open source pub-sub messaging and streaming platform for real-time workloads, managing hundreds of billions of events per day.
Zenaton is a developer tool and hosted workflow engine for writing, running and monitoring all of your background processes whether it is a single task or a long running workflow. It allows developers to easily integrate third party services and APIs iby triggering tasks and...
ØMQ is a high-performance asynchronous messaging library aimed at use in scalable distributed or concurrent applications. It provides a message queue, but unlike message-oriented middleware, a ØMQ system can run without a dedicated message broker.
Simple, efficient background processing for Ruby. Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails to make background processing dead simple.
Dedicated platform to send and receive messages within your applications. It has simple REST API and clean web UI. It allows to control access to your queues with managed access tokens.
Database based asynchronous priority queue system -- Extracted from Shopify - collectiveidea/delayed_job
Spooled is a high-performance, multi-tenant job queue system designed for reliability, observability, and horizontal scalability.
Zeplo lets developers add retry, delay, queue and schedule to HTTP endpoints without setting up Redis, RabbitMQ or SQS. Just prefix any HTTP endpoint with zeplo.to/ and the request is queued.
cTRL is a server for remote execution of pending tasks and commands in real time, supporting a queue with continuous thread limiting and throttling.
United States
Canada
United Kingdom
RabbitMQ is for messaging, Celery is for running tasks