Summary of Vijay Nair - Implementing Event Driven Architectures with Axon and Kafka

00:00:00 - 00:30:00

In the video, Vijay Nair discusses how to use Axon and Kafka to create an event-driven architecture. He explains that Axon is a fast and reliable event store, while Kafka is a platform for managing events and providing stream-based processing. He demonstrates how the two tools can be combined to create a powerful event sourcing platform.

• 00:00:00 Vijay Nair is an architect at large and will be talking about the usage of Axon and Kafka together to implement robust event-driven architectures. He will discuss what each tool does best, how they fit within the whole event-driven architecture paradigm, and how they work well together. Finally, he will talk about how these two tools are easy to combine and how they result in a robust, even-driven microservices infrastructure.
• 00:05:00 Vijay Nair discusses the two event-driven architecture patterns, even streaming and sourcing, which are gaining in popularity due to their scalability and reactivity. He explains that even streaming advocates the design and development of applications by publishing events as well as subscribing to a constant stream of events, while sourcing states that the state of an application and the state of the application is generally determined by the state of its various entities and aggregates. Event sourcing is a domain-driven design-inspired architectural pattern that mandates the state of the application and its various aggregates be represented by events, rather than explicitly stored in a database.
• 00:10:00 Event sourcing is a technique used to build the state of an aggregate by storing events as they happen. This is done in a fast and append-only fashion, and Domain Driven Design is important for modeling the aggregates. Finally, a cqrs implementation is needed to handle commands, queries, and events.
• 00:15:00 Vijay Nair explains that there is a logical investment in Kafka today as a central event processing system, even if you're not using the event sourcing pattern. He provides a capability map of the necessary features of a physical and logical infrastructure for event sourcing.
• 00:20:00 Vijay Nair discusses the benefits of using event-driven architectures with Axon and Kafka, and how they can be implemented with single partition topics and aggregate stores. However, when it comes to even sourcing, KAFKA is not a suitable tool because of its limitations in terms of operations and API. Axon provides a framework to help build out an event sourcing infrastructure, and is already built-in to Kafka.
• 00:25:00 Axon provides a fast, reliable, and scalable event store, while Kafka is a platform for managing events and providing stream-based processing. Axon and Kafka can be combined to create a powerful event sourcing platform.
• 00:30:00 In this video, Vijay Nair discusses how Axon and Kafka can be used to implement event-driven architectures. Axon provides a connector to integrate with Kafka, which makes it possible to persist events and have them delivered to downstream systems.