Event sourcing is about persisting events for each change to application state, instead of just persisting the current state. Event sourcing can be helpful for auditing purposes, and to analyze or rebuild previous system states for business analysis. BDD has been made popular by Dan North as a way to lift TDD to the application level and guide development through examples that are understandable by programmers, testers and domain experts alike.
This talk examines the relationship between event sourcing and BDD. How can BDD examples guide the development of event sourced applications? How do commands, events and state tie together these practices?
Below are the key takeaways from this session:
1. Get introduced to event sourcing and BDD
2. Explore the relationship between BDD and event sourcing using Gherkin examples
3. Learn how event sourced systems can be tested with BDD
4. Learn how commands, events and state matter in event sourcing and BDD
Bertil Muth has been programming since the early 90s. He has a computer science degree from the Technical University of Munich. In 2004, he helped build the software of a ground station of a satellite communication system. Since then, event-driven systems have been fascinating to him. He worked in various roles: as a programmer, a tester, an architect, a Scrum Master and a consultant.