As traditional and monolithic landscapes are rapidly changing to landscapes with lots of microservices, technical solutions are becoming more and more decentralized and the number of data streams and their associated data handling is growing exponentially. Within these microservices landscapes, there are a variety of applications, frameworks and data sources, each exchanging data and responsible for a specific part of the overall landscape. In a chain of applications and services, each link in the chain may have a need for data from other sources and may also be a source of data itself. The integration pattern Event streaming can provide a solution for this.

Event streaming allows you to publish data without building specific integrations between 1 or more applications. The source publishes the data in the form of events and other applications can subscribe to them. The source knows who the customers are but does not maintain a relationship with them, it publishes data and the customers then decide for themselves if and how they process this data. This also means that data is offered 'streaming' and not in the form of a guaranteed delivered and processed message. Event streaming is therefore ideally suited for, for example, master data or transactional data distribution and is used to exchange data and events reliably, asynchronously and flexibly between applications.