taskforcesh/bullmq

BullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQL

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 7th, 2026
Created on December 19th, 2018
Open Issues & Pull Requests: 385 (+0)
GitHub issues: Enabled
Number of forks: 680
Total Stargazers: 9,377 (+0)
Total Subscribers: 42 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

BullMQ is a distributed message queue and batch processing system for Node.js, Python, .NET, Elixir, Rust, and PHP that uses Redis or PostgreSQL as its backing store.

The tool addresses the need for reliable background job processing and task scheduling across multiple programming languages. It works by leveraging Redis or PostgreSQL to maintain queue state and job data, with language-specific client libraries that communicate with the same underlying queue infrastructure. The design emphasizes atomicity and stability to ensure jobs are processed reliably without data loss or duplication.

Teams should adopt BullMQ if they need cross-language job queue support or are already invested in a specific language ecosystem where the tool offers a native implementation. It suits projects requiring distributed task processing, delayed job execution, and batch operations. The tool's multi-language availability means a single queue backend can serve microservices written in different languages, reducing operational complexity compared to maintaining separate queue systems per language.

The project maintains active development across multiple language implementations simultaneously, with coordinated updates to the Node.js, Python, Rust, Elixir, .NET, and PHP versions. The codebase uses semantic versioning for releases and maintains high test coverage. Development activity spans the core repository and language-specific subdirectories, indicating sustained investment in keeping all implementations current and feature-parity across platforms.