These events are currently sent one by one by ReactiveEventMessagePublisher, which is the case of Http Smallrye connector heavily affects system throughput, which in turn increase memory consumption because of event queuing.
One possible improvement is to set the message body to the entire collection, minimizing the number of external calls. However this will affect consumers. For example, in DataIndex, ReactiveMessageEventConsumer will have to be changed to check if the message body contains one event or a collection of them.
EventPublisher has the list of events generated at the end of a UnitOfWork
These events are currently sent one by one by ReactiveEventMessagePublisher, which is the case of Http Smallrye connector heavily affects system throughput, which in turn increase memory consumption because of event queuing.
One possible improvement is to set the message body to the entire collection, minimizing the number of external calls. However this will affect consumers. For example, in DataIndex, ReactiveMessageEventConsumer will have to be changed to check if the message body contains one event or a collection of them.