3.1 Event driven architecture theory

Mon, 01 Jan 0001 00:00:00 +0000

3.1.1: Event driven architecture

When designing applications or software systems we usually tend to follow a very imperative way of building our components. Especially in monolithic applications, the communication between two components will often come from function or method calls from one component to another. Even when we follow a microservice architecture the most intuitive way for most people would be to simply replace these calls with REST calls. In theory, this is a valid approach and will often be the first step when migrating a monolith towards a microservice approach. The downside, however, will be the same. Whenever two components talk directly to each other they rely on an often synchronous direct communication channel. What happens if the other component is not available?

3.2 Event driven architecture with Apache Kafka

Mon, 01 Jan 0001 00:00:00 +0000

This lab gives you an introduction to event-driven architecture with Apache Kafka. You will deploy an event-driven version of the producer-consumer application from lab 2 .

3.2.1: Apache Kafka

In this section, we are going to deploy an Apache Kafka cluster with the Strimzi Operator and use it to distribute our events between the microservices. In modern large scale applications, messages must be processed, reprocessed, analyzed and handled - often in real-time. The key design principles of Kafka were formed based on the need for high-throughput architectures which are easily scalable and provide key features to store and process streamed data.

3. Event driven architecture on Application Migration and Modernization Techlab

3.1 Event driven architecture theory

3.1.1: Event driven architecture

3.2 Event driven architecture with Apache Kafka

3.2.1: Apache Kafka