Airflow vs Resque: What are the differences?
Developers describe Airflow as "A platform to programmaticaly author, schedule and monitor data pipelines, by Airbnb". 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. On the other hand, Resque is detailed as "A Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later". Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.
Airflow and Resque are primarily classified as "Workflow Manager" and "Background Processing" tools respectively.
Airflow and Resque are both open source tools. It seems that Airflow with 13K GitHub stars and 4.72K forks on GitHub has more adoption than Resque with 8.54K GitHub stars and 1.57K GitHub forks.
Airbnb, Slack, and 9GAG are some of the popular companies that use Airflow, whereas Resque is used by MAK IT, NoRedInk, and Yummypets. Airflow has a broader approval, being mentioned in 72 company stacks & 33 developers stacks; compared to Resque, which is listed in 34 company stacks and 8 developer stacks.