Event-sourced architecture stores all changes to an application’s state as a sequence of immutable events instead of storing a single mutable status. In this talk, we will explore how this approach can help eliminate race conditions, increase visibility into the system and decouple use cases, making changing business requirements easier to handle. Let’s dive deeper into it by studying a case of the transition from state machine to event-sourced architecture in a real-world FinTech service processing customer payments.
In an event-driven landscape where high-traffic systems usually grab the spotlight, we highlight how event architectures benefit scenarios with less traffic too. We will dig deep into states and events and address the common confusion around events and commands, which are sometimes used interchangeably. The talk will discuss both the benefits and challenges of event sourcing.
After this talk, I want you to feel confident adding event sourcing to your set of programming tools and deciding when to apply it.
Target Audience: This presentation is aimed at medior programmers with an understanding of system design and architecture. Concepts will be explained clearly, making the session beneficial for junior programmers as well.