Living at the moment is great—until production throws an error and your logs shrug back: ¯\_(ツ)_/¯

Traditional systems forget the past. Event Sourcing doesn’t. It records every change like a journal, making debugging,
audits, and insights much easier—and sometimes even fun. But beyond the benefits, it also comes with real trade-offs
every developer should know before adopting it.

In this session, we’ll explore the core building blocks of event-sourced systems—commands, events, read models,
projectors (reactors), and the event store—and see how they fit together in practice. We’ll unfold practical patterns by
applying them to a live-coded Tic-Tac-Toe game, step by step.

What you’ll learn
• Develop a clear mental model of Event Sourcing and recognize when (not) to use it
• Apply practical patterns immediately in your own systems
• Understand both the superpowers and the pitfalls of event-sourced architectures

Anyone (backend developers, cloud developers, architects) who is curious about event-driven systems and wants to move
beyond the theory into real-world applications. No prior Event Sourcing experience required—just curiosity and maybe a
sense of humor.