Motivation

We have faced the following scenario/problem in a lot of situations with KStreams:
- Huge incoming data being processed by numerous application instances
- Need to aggregate different fields whose records span all topic partitions (something like “total amount spent by people aged > 30 yrs” when processing a topic partitioned by userid).