kubemq-io/kubemq-bridges
KubeMQ Bridges is a message routing and transformation service that connects KubeMQ clusters by bridging, replicating, and transforming data flows between sources and targets. It supports diverse message types including events, commands, queries, and queues, utilizing middleware for retry, rate limiting, and metrics. The system features hot-reloadable configuration, structured logging, and a comprehensive HTTP API for monitoring and management.
60.3
Adequate · 3 August 2026
5.7k
lines of production code
Go
primary language
1
bus factor · 5 authors in all
3
measurements over time
How it got here
2020 · Initial release of KubeMQ Bridges
This period marks the initial release of KubeMQ Bridges, introducing a comprehensive framework for bridging, replicating, and transforming messages between KubeMQ clusters. The work established the core architecture, including unified source and target connectors for commands, queries, events, and queues, alongside essential middleware for logging, metrics, and rate limiting. The release also included cross-platform support, hot-reloading capabilities, and example applications demonstrating multi-cluster data flows.
24 changes
2021 · new packages and logging improvements
This period focused on introducing new utility packages for UUID generation, browser handling, and configuration building. It also enhanced observability by adding specific log files for KubeMQ bridge errors and adapting logging formats for containerized environments.
5 changes
Survey your own repository
kubemq-io/kubemq-bridges was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 453541be86 — the exact code this score is about.
- Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.