In a 2005 essay, Martin Fowler described "Event Sourcing" as an architectural pattern wherein "all changes to application state are stored as a sequence of events". Sounds simple, right? Event-Sourcing provides many powerful capabilities, including the ability to query data from any moment in time, replay past events, and reconstruct the state the application (including historical data) after a disaster. How can you design your data model and your application architecture to take advantage of these capabilities? And what about the pitfalls of event-sourcing and event-driven design, such as transient state changes, concurrent event-processing, and brittle event schemas?

In this presentation, you'll learn what Event Sourcing is, how you can benefit from it in your applications, and how to design for resiliency and respond effectively to change. You'll also learn how to implement and leverage Command and Query Responsibility Segregation (CQRS) to cleanly separate between your event-sourced write models and more typical read models such as REST APIs.