Event-driven architecture

There are other architectural styles besides microservices, monolithic, and multi-tier applications – for example, Event-Driven Architecture (EDA). EDA is a pattern around the publication, processing, and persistence of events. The backbone is a message broker – for example, Apache Kafka – and individual services or components can publish events (a publisher) or subscribe to events (a subscriber).

EDA can be a good fit with a microservices-based approach – but it can also be used with other architectural styles. It can help you to keep consistency in loosely coupled components or services, and it can scale perfectly horizontally due to the asynchronous nature of events and is therefore well suited for solutions that process big amounts of data in motion, such as IoT solutions that process sensor data in near real time.

Especially in cloud-native environments, EDA can help you to move fast and to build loosely coupled and global...