apache/kafka
This system is a distributed event streaming platform that manages high-throughput, low-latency data pipelines. It provides a Java-based client library for producing and consuming messages with advanced features like transactions, share groups, and pluggable security mechanisms. The platform also includes a connector framework for integrating external systems and a comprehensive administrative API for cluster management, authorization, and configuration.
67.6
Adequate · 29 July 2026
631k
lines of production code
Java
primary language
29
bus factor · 1,640 authors in all
3
measurements over time
How it got here
2011–2014 · KRaft migration and legacy code removal
This period focused on the architectural shift from ZooKeeper to the KRaft metadata quorum, which required removing the legacy Scala-based server, client, and tooling code. The team simultaneously modernized the Java client API, introduced the Share Consumer, and cleaned up the codebase by eliminating obsolete integrations and test suites.
85 changes
2015–2018 · Security and Connect API expansion
This period focused on significantly expanding the Kafka client's security capabilities by introducing pluggable authentication mechanisms including SCRAM, PLAIN, and OAuth/OIDC, alongside a new ConfigProvider interface for dynamic configuration. Concurrently, the Kafka Connect API was substantially extended with new interfaces for data models, transformations, and health monitoring, while the AdminClient received a major internal refactoring to support complex administrative operations.
105 changes
2019–2024 · KRaft migration and modularization
This period was defined by the extensive migration to the KRaft metadata quorum, introducing a new metadata module and refactoring the server architecture to support a controller-based cluster without ZooKeeper. Concurrently, the codebase underwent significant modularization, splitting the monolithic core into dedicated modules for transaction, group, and share coordination, while introducing pluggable APIs for authorization, client quotas, and Connect predicates.
90 changes
2025–2026 · Test infrastructure and API stability
This period focused on expanding test coverage and infrastructure, introducing new classes for cluster management, selective test execution, and mock implementations. Simultaneously, the project refactored internal package structures to restrict visibility of non-public APIs and enhanced automated checks to prevent internal API leaks.
22 changes
Survey your own repository
apache/kafka 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 29 July 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 678c0e07e4 — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.