Code Conversations

In this gentle introduction to Event-Driven Architecture, we will explore real-world use cases and main concepts such as Event Notification, CQRS, Event Sourcing, etc. We'll discuss common technologies and patterns, such as Messaging with RabbitMQ and Streaming with Kafka.

This video explores the fundamentals of event-driven architecture (EDA), highlighting its increasing popularity, particularly for larger and more complex systems. The video contrasts EDA with traditional command-oriented programming and emphasizes its benefits in decoupling code, promoting separation of concerns, and enhancing system scalability and resilience. The speaker provides practical advice for implementing EDA, advocating for modeling events based on real-world business logic and illustrating how this approach facilitates incremental system growth and adaptation. The video also introduces concepts like event storming and domain-driven design, which can be used to design systems that are more robust and adaptable.

The video from the YouTube channel "Alex Hyett" explores the concept of event-driven architecture in the context of microservices. The video highlights the benefits of event-driven architecture over traditional API-driven models, emphasizing its ability to decouple components, improve scalability, and facilitate dependency inversion. However, the video also acknowledges potential drawbacks such as the possibility of data inconsistency and the need for item potency in handling duplicate events. The video concludes by emphasizing the importance of considering the complexity and overhead associated with event-driven architecture before adopting it, suggesting it might not be the optimal choice for systems that don't require significant scalability.

We deep dive in the differences between two architectural approaches used for building applications: event-driven architecture (EDA) and request/response architecture (RR).