Event Sourcing: Rethinking How We Store Data - Brent Stewart

Event Sourcing: Rethinking How We Store Data
Most applications are built to store “what is.” Event Sourcing takes a different approach. Instead of persisting the current state, we persist the facts of what happened and let state be derived from that history.
In this session, we’ll explore the Event Sourcing pattern and unpack how modeling behavior, rather than focusing on state, changes the way we design systems. We’ll look at the core ideas behind events, aggregates, replay, and projections, and discuss the trade-offs that come with adopting this approach.
Whether you’re curious about the pattern, considering adopting it, or wondering if it’s worth the added complexity, this talk will help you build a clearer mental model of where it fits and where it doesn’t.
State tells you the result. Events tell you the story.

Brent Stewart
As a professional software developer with over two decades of experience, Brent has seen many development trends come and go and learned that there is not a shortcut to being a great developer. He enjoys teaching and tries to mentor others whenever he can. When he is not speaking at conferences around the Midwest he can be found helping organize the Kansas City .NET User Group.
He is a creator at heart and has started multiple businesses over the years in a variety of industries. His latest venture is Alien Arc Technologies which allows him to take his ideas and give them form. He loves quality in all things and always try to provide the best quality in everything he does. If it is worth doing, then it is worth doing right.

See Sharper Lighting Talk
Don’t Throw That! Exceptions and Error Handling in .NET - Duane Newman
Exceptions are a powerful feature in .NET—but they’re often overused, misunderstood, and misapplied. In this lightning talk, we’ll take a practical look at what exceptions are actually for, when they’re the right tool, and when they’re not. You’ll learn why using exceptions for normal control flow can hurt performance and readability, how alternative return types can lead to clearer code, and how to design APIs that make failure explicit instead of surprising. By the end of the session, you’ll have a better mental model for error handling in .NET—and the confidence to know when not to throw.

Sponsored & Hosted By: Alien Arc Technologies
Location Provided by: Quest Analytics