Topic starter
24/06/2026 9:11 pm
TL;DR: Teams can reduce Kafka clusters, topic sprawl, glue code, and ACL complexity by shifting isolation, filtering, protocol mediation, access control, and discovery into Kong Event Gateway, according to Kong. The underlying problem is not Kafka performance alone, but the governance overhead created when event access, identity, and distribution are managed inconsistently across teams.
Editorial analysis by NHI Mgmt Group, based on content published by Kong: “# 5 Steps to Immediately Reduce Kafka Cost and Complexity”.
Key questions
Q: How should teams reduce Kafka cost without creating more governance sprawl?
A: Teams should reduce Kafka cost by treating isolation, filtering, access control, and discovery as governance problems rather than infrastructure defaults.
Q: Why do duplicate Kafka topics and clusters become an operational risk?
A: Duplicate topics and clusters increase risk because every copy creates another place where ownership, permissions, documentation, and retirement must be managed.
Q: What breaks when Kafka access control is enforced only through broker-level configuration?
A: Broker-only control often breaks down when organizations need consistent governance across many teams, topics, and consumers.
Practitioner guidance
- Map Kafka tenancy to logical isolation first Review whether new Kafka clusters are being created for governance reasons that a shared policy layer could absorb.
- Replace duplicate topics with filtered views Identify topics that exist only to serve different consumer subsets and evaluate whether policy-based filtering can expose those slices from a single source topic.
- Move access enforcement to one policy plane Standardise OAuth2, JWT, API key policy, and RBAC enforcement where Kafka and API access converge so audit trails and permissions are reviewed in one place.
Bottom line: The article frames Kafka cost as a governance problem driven by duplicated controls, not as a throughput problem.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 6:15 am
Kafka governance fails when isolation is treated as an infrastructure problem instead of an access problem. The article shows a familiar pattern: teams duplicate clusters because they do not trust shared governance to preserve separation. That assumption drives cost and operational overhead more than Kafka itself does. The better framing is that tenancy, audit, and entitlement boundaries are the real control plane, and practitioners should design around that reality.
A question worth separating out:
Q: What is the difference between Kafka ACLs and API-layer access control?
A: Kafka ACLs protect broker-native access, while API-layer access control can centralise identity policy, auditing, and reuse across Kafka and non-Kafka consumers. The difference matters when the goal is to govern multiple access patterns through one control plane instead of maintaining a separate permission model for every broker interaction.
👉 Read our full editorial: Kong Event Gateway for Kafka: cutting cost without losing control