Connecting different Infrastructures
June 03, 2015 17:33
I deploy to Heroku. However, my applications require full linux applications that cannot be deployed to Heroku. I deploy them to Rackspace.
Then Heroku and Rackspace communicate over IronMQ. Problem solved.
Kalibrr uses Celery
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.
Cloudify uses Celery
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.
MOKA Analytics uses Celery
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
jegesh uses Celery
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.
ruleant uses Celery
Using Celery, the web service creates tasks that are executed by a background worker. Celery uses a RabbitMQ instance as a task queue.
InsideSales.com uses NSQ
The built-in Gamification that comes with our Playbooks application uses NSQ for work queues and microservice communication.