bloomberg/blazingmq

A modern high-performance open source message queuing system

Owned by Bloomberg

View on GitHub ↗Jump to charts ↓Open shareable report →

bloomberg/blazingmq has 3k+ stars and 200+ forks on GitHub, is written in C++, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on July 11th, 2023
Open Issues & Pull Requests: 116 (+0)
GitHub issues: Enabled
Number of forks: 201
Total Stargazers: 3,216 (+0)
Total Subscribers: 22 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.2 hours
Mean response time: 52.8 days
90th percentile: 212.7 days
Tracked items: 78

Maintainer activity

11 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 25
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 485 days
Stale 30+ days: 21
Stale 90+ days: 18

Recent activity

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

Top labels

  • bug (28)
  • enhancement (13)
  • good first issue (13)
  • A-Broker (11)
  • A-Client (6)
  • A-Testing (6)
  • A-Other (4)
  • A-Build (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

BlazingMQ is a distributed message queuing system that provides durable, fault-tolerant, and highly available message queues for asynchronous communication between application services.

The system solves the problem of enabling loosely-coupled communication between producers and consumers by storing messages until recipients retrieve and process them. This temporal and spatial isolation allows applications to operate independently. BlazingMQ implements various message routing strategies including work queues, priority routing, fan-out, and broadcast modes. The framework also includes features such as compression, strong consistency guarantees, and poison pill detection to handle edge cases in message processing.

BlazingMQ suits teams building distributed systems that require reliable message delivery and flexible routing patterns. The message broker is implemented in C++, with client libraries available in C++, Java, and Python, making it accessible across different technology stacks. Organizations with production workloads requiring high performance and fault tolerance will find the system's emphasis on efficiency and reliability relevant. The tool is particularly appropriate for teams already familiar with message queue concepts and seeking a system with strong consistency properties rather than eventual consistency trade-offs.

The project maintains active development with regular updates to the codebase. The tool has undergone extensive production validation over multiple years at a major financial institution, demonstrating stability in demanding environments. Documentation is comprehensive and includes quick-start guides with Docker-based local experimentation paths, as well as intermediate and advanced feature walkthroughs. The project accepts community contributions and maintains clear security vulnerability reporting procedures.