Clarify ordering guarantees out externalized events

Hi, I am trying to understand the ordering guarantees of externalized events, in particular whether it is guaranteed that two events originating from two concurrent requests are sent to Kafka (or whatever message broker is used) in the exact same order as the database transactions are committed? This is vital for ensuring a consistent state across the database and the Kafka event consumers. Are the transaction listeners used for sending the message somehow synchronized? Thanks for any clarifications!

Start by tracing the externalized-event transaction listeners and the broker publication path mentioned in the issue. Check the existing Spring Modulith documentation and references for transaction synchronization and event publication, then document the ordering guarantees for concurrent database transactions and whether listener synchronization applies.