gazette/core
This system is a distributed data ingestion and processing platform that manages the lifecycle of journal-based streams. It provides a broker service for high-throughput, fault-tolerant storage of append-only logs across multiple cloud and local storage backends, alongside a consumer runtime for stateful, exactly-once processing of those streams. The architecture includes a CLI tool for configuration and monitoring, a distributed allocator for shard management, and robust recovery mechanisms for both broker and consumer components.
53.1
Adequate · 3 August 2026
28k
lines of production code
Go
primary language
1
bus factor · 39 authors in all
3
measurements over time
How it got here
2015–2019 · V2 architecture and distributed storage
This period focused on the comprehensive transition to the V2 architecture, introducing a new consumer framework with robust shard lifecycle management and recovery capabilities. The work expanded the broker's capabilities with distributed allocation, flow control, and multi-backend storage support, while establishing a standardized application bootstrapping and testing infrastructure.
36 changes
2020–2025 · Broker protocol and storage expansion
The project expanded its broker protocol with new extension packages and introduced a modular storage backend abstraction supporting multiple cloud and local storage providers. Additionally, the codebase added comprehensive CLI tools for journal and shard management, alongside robust authentication mechanisms including JWT and bearer token support.
4 changes
Survey your own repository
gazette/core 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 e54beb5c6e — 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.