In Kafka, it's generally recommended to map one table to one topic. However, what if the order of events across multiple tables is important for a specific key, such as CompanyId?
For example, consider the following scenario: events for a CompanyId must be processed (consumed) in order, even though they originate from different tables. Partitioning is configured such that each partition corresponds to a specific CompanyId:
Is it possible to ensure that the order of events (transactions) for each CompanyId is reliably preserved across all relevant tables? For instance, achieving something like this:
I use Avro for schema control.

