Over the past few years, I’ve been researching Event Sourced applications, and have been quite intrigued with their ease of development, inherit auditability, etc.
I’ve had the privledge of collaborating with several people in the industry:
All of these gentlemen either work-for, developed, or consult on event sourcing solutions, with two of the gentlemen working for EventStore. Through the process, I’ve watched all of Greg’s videos on the theory of event sourcing, and had a less than optimum experience with my first attempt at trying to learn event sourcing.
Lately, I’ve been getting guidance from Chris Condron on his toolkit Reactive Domain as well as best practices while implementing the toolkit in an existing solution.
Throughout this series of articles, the hope is to document my learnings, as well as the education that Chris has been so gracious to provide me.
These articles are from the point-of-view of a traditional 9-5 developer that takes their toolkit of:
The goal is to finish the application where the use case will be:
I hope this helps others as they begin the process of learning and otherwise implementing EventStore and event sourcing in their companies.