Protocol schemas field by field, wire format byte by byte, and the KIP behind every change.
Built by Conduktor, the enterprise platform for Apache Kafka.
See Conduktor →Every config property side by side across releases, with the defaults that moved highlighted where they moved.
Every API, field by field, straight from the message schemas — with the KIP behind each change.
What a request actually looks like on the socket: byte offsets, varints, tagged fields, annotated.
Which protocol versions a broker speaks — the table you want before pointing an old client at a new cluster.
Every improvement proposal, summarised and tagged, with the release it actually landed in.
Every protocol error code: what triggers it, whether retrying helps, and the command that confirms it.
The stack trace you just pasted into Slack, with the cause, the fix, and a real example.
Pick two releases, see exactly what moves: config diffs, protocol bumps, removals, and the KIPs behind them.
Tuning profiles for throughput, latency, durability and cost — each one telling you what it costs.
Opinionated ResourcePolicy YAMLs, ready to drop into a self-service catalog.
CDC across every supported connector: config matrix, event envelope, snapshot modes, errors.
Chain Connect transforms against a real record and watch the output change at every step.
Paste a query, get its topic flow, window semantics, state growth and the warnings nobody mentions.