python-arq/arq

Fast job queuing and RPC in python with asyncio and redis.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 59 minutes ago
Added to GitGenius on September 23rd, 2026
Created on July 21st, 2016
Open Issues & Pull Requests: 109 (+1)
GitHub issues: Enabled
Number of forks: 222
Total Stargazers: 3,014 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 39.9 days
Mean response time: 175.2 days
90th percentile: 502.0 days
Tracked items: 31

How this project is maintained

96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 75% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 26
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 695 days
Stale 30+ days: 25
Stale 90+ days: 24

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

arq is a job queue and RPC framework that enables fast asynchronous task processing in Python using asyncio and Redis as the backing store.

The tool addresses the need to offload long-running or resource-intensive operations from the main application thread. It works by allowing developers to define async functions as jobs, enqueue them to a Redis-backed queue, and process them concurrently through worker processes. The framework handles job serialization using msgpack, manages task execution with asyncio, and provides mechanisms for both fire-and-forget job execution and synchronous RPC-style calls that wait for results.

arq suits projects that need distributed task processing with Python's async ecosystem. It is particularly appropriate for applications already using asyncio and Redis, where developers want a lightweight alternative to heavier job queue systems. The tool's focus on async-first design makes it well-suited for I/O-bound workloads and microservices architectures that benefit from concurrent task handling.

The project is in maintenance-only mode, meaning it receives bug fixes and critical updates but is not undergoing active feature development. This signals a mature, stable codebase where the core functionality is considered complete and the maintainers are focused on reliability rather than expansion.