Start with a change in the business
Materials arrive at the warehouse. A contract is approved. A period is closed. These are events after which another team needs to know or do something. When connections between systems are built around these changes, there is no need to transfer the full context manually every time.
Separate the source from the recipient
The source publishes an event, and interested systems process it according to their own logic. The warehouse records receipt, procurement updates the delivery status, and analytics receives a new fact. Each system retains its own area of responsibility.
Agree on data in advance
An exchange bus alone does not resolve different interpretations of data. You need identifiers, event descriptions, format versions and rules for reprocessing. Otherwise, the same ambiguity simply moves into the integration.
How this relates to EcoPro
In EcoPro architecture, MB Kafka connects the products. MDM manages consistent reference data, while DWH provides history and data for analytics. These roles complement each other: transport, shared definitions and shared memory.