You can do it, but the performance trade off will be very costly. There is
no ordering guarantee between partitions, so you would have to work with
topics with only one partition. I believe you would also need to set the
batch.size in the producer to 1 to ensure the messages aren't re-ordered
withi
Afaik that is not possible out of the box as that would require
synchronization across multiple threads/instances. The throughput of such
an approach would be terrible as the parallelism of KStreams is tightly
coupled with the number of partitions.
I'd say if you need such ordering you should reco