Spring Cloud Stream | Batch | TPS | Tuning

Hi @kirthi ,

My guess is that the performance bottleneck is in the Cloud Stream framework itself as I believe it is what sees a collection of messages and then sends them to our binder to publish as individual messages. I imagine that this isn’t a heavily used feature of the framework so maybe there are some easy options for performance improvements there. Have you opened an issue on the Spring Cloud Stream repository:

?

Striking this suggestion out as it looks like the issue was addressed.