Ross ROSS = Recommend OSS · open-source software intelligence for agents

bloomberg/blazingmq

A modern high-performance open source message queuing system observed · 2026-08-28

github.com/bloomberg/blazingmq · homepage · C++ · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

73/100

  • Activity 99
  • Release rhythm 35
  • Longevity 82

Flags: no_releases

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 1149
  • days_rel: n/a
  • days_push: 7
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

3208 stars · 193 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

BlazingMQ is a distributed, high-performance message queuing system written in C++, providing durable, fault-tolerant queues with rich routing strategies. It includes the message broker, a C++ client library, and a CLI tool, with Java and Python clients in separate repositories.

Use cases

  • decouple producer and consumer services with asynchronous messaging
  • build work queue pipelines for distributed task processing
  • fan-out messages to multiple consumer groups
  • run a self-hosted message broker with strong consistency and replication
  • reduce network bandwidth in high fan-out workflows with multi-hop topology
  • replace Kafka or RabbitMQ for latency-sensitive messaging workloads

When to choose

  • you need durable, highly available queues with strong consistency
  • you want low median and p99 latency without external dependencies like ZooKeeper
  • you need flexible routing strategies such as work queues, priority, fan-out, or broadcast
  • you are building event-driven microservices in C++, Java, or Python

When to avoid

  • you need a managed cloud-native messaging service
  • your stack requires clients in languages other than C++, Java, or Python
  • you need a lightweight embedded queue rather than a distributed broker cluster
  • you rely on a large ecosystem of third-party connectors and tooling

Facets

service · maturity stable

message-queue middleware streaming microservices backend developer-tools cpp cross-platform message-broker event-driven-architecture work-queues fan-out high-throughput clustering replication messaging linux

2 sources

Member repositories

RepositoryRoleHealth v2
bloomberg/blazingmqmain73

For agents

markdown · JSON · MCP: product_card(name="bloomberg/blazingmq")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem