Colocating Input Partitions with Kafka Streams When Consuming Multiple Topics: Sub-Topology Matters!
Explores a production issue where Kafka Streams failed to colocate matching partitions from two topics on the same instance, breaking cache locality. The root cause was implicit creation of separate sub-topologies for each topic. The solution involved replacing a local Guava cache with a shared Kafka Streams state store, which
Table of contents
Expedia Group Technology — EngineeringUnderstanding how sub-topology design influences partition co-locationGet Vishal Sharma’s stories in your inboxSort: