Kafka performance problems are usually design problems: hot partitions, oversized messages, or consumers that cannot keep pace with producers.
We design topics around access patterns, not org charts. Partition keys must reflect real distribution, and replayability must be tested—not assumed.
Operations matter as much as code: lag alerts, broker health dashboards, and runbooks for rebalancing are part of the product, not optional ops work.
