/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

apache/kafka

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:47:49.447Z

1mo ago

apache/kafka

Apache Kafka is a very active Apache project for distributed event streaming. This repo is the main upstream codebase, on `trunk`, with a large contributor base and ongoing commits as of 2026-03-30. It looks suitable if you want a fork of a mature, high-activity JVM platform with strong documentation and broad infrastructure around build, test, Docker, and tooling support.

Loading tags...

Stars32,234

Forks15,070

Default branchtrunk

Last pushed2026-03-30T15:38:08Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if you want a production-hardened Kafka derivative with operational fixes and can accept major upstream lag. Choose upstream if you want the latest Kafka features, active trunk alignment, and lower merge debt.

Prefer this fork only if you specifically need its storage-tiering and multi-disk design. If you want current Apache Kafka features, bugfixes, and lower maintenance risk, upstream is the safer choice.

Prefer upstream Kafka unless you specifically need this fork's older, heavily modified baseline. Choose this fork only if you are willing to own the maintenance burden and do not need current upstream fixes.

Prefer upstream Kafka unless you specifically need this old snapshot or its local customizations; this fork is too stale for normal production adoption and is best treated as legacy code, not a current platform choice.

Choose upstream unless you specifically need the Microsoft mirror or an older divergent codebase. For most adopters, this fork is too stale and too far from current Kafka to be a safe default.

Prefer this fork if you want Kafka with extra operational automation and Confluent-oriented infrastructure. Prefer upstream if your priority is the newest canonical Apache Kafka line with the least fork-specific surface area.

Choose this fork only if you specifically want a stale Kafka snapshot or mirror. If you want an adopter-friendly Kafka distribution, current upstream is the better choice.

Prefer this fork only if ZooKeeper removal is the primary requirement and you are comfortable owning a long-lived, heavily divergent codebase. For most production adopters, upstream Kafka is the safer choice because this fork is far behind and likely missing many modern features and fixes.

Prefer upstream Apache Kafka unless you specifically need this legacy, heavily diverged snapshot. This fork is stale and materially behind current Kafka, so it is a poor choice for new deployments or active maintenance.

Choose this fork if your goal is study and annotation. Choose upstream if you need current Kafka features, fixes, and operational reliability.

Fork comparison

linkedin/kafka

54/100

slowing

significant_divergence

Choose this fork if you want a production-hardened Kafka derivative with operational fixes and can accept major upstream lag. Choose upstream if you want the latest Kafka features, active trunk alignment, and lower merge debt.

Likely purpose

A production-hardened Kafka variant for LinkedIn-style operational needs, with custom fixes around topic creation, log handling, throttling, metrics, and coordinator behavior.

Best for

Platform teams maintaining a Kafka deployment with LinkedIn-style operational requirements.; Adopters who value stability, logging/metrics tweaks, and failure-handling changes over upstream freshness.; Organizations comfortable carrying fork-specific maintenance and integration work.; Teams porting or preserving an older Kafka branch with localized hotfixes.

Additional features

Track successful auto-topic creations.
Warn when a leader truncates its current log.
Retry log cleaning failures before marking a partition uncleanable.
Enforce safer topic replication-factor bounds during creation.
Handle LogDirFailureHandler exceptions more defensively.
Preserve more reliable behavior during throttling and broker restart edge cases.],

Missing features

It is far behind upstream trunk and appears to miss hundreds of newer Apache Kafka commits.
It likely lacks newer upstream coordinator, streams, docs, and monitoring changes present in current trunk.
It is anchored on an old `3.0-li` branch, so adopters should expect older APIs and fewer recent platform updates than upstream.
Upstream maintenance and release flow is not reflected here, so newer bug fixes and compatibility work from current Kafka may be absent.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream operational features such as auth, admin, or session handling may be reduced or absent.

Strengths

Operational hardening and defensive fixes are prominent.
The fork appears tuned for reliability under failure, throttling, and log-management edge cases.
It preserves a large, mature Kafka codebase while adding internal guardrails.
The change history suggests it has been used in real production scenarios, not just as a cosmetic fork.

Risks

Large divergence makes upstream merges harder and raises long-term maintenance cost.
Being behind trunk means missing recent fixes, features, and compatibility work.
Custom behavior may surprise users expecting stock Apache Kafka semantics.
The old default branch suggests this is not the best choice if you want an actively tracking upstream fork.