AspNetCoreEventSourcing is a prototype project. It it an implementation of event sourcing of a simple business flow. Its purpose is a learning exercise for myself, with an aim of determining if it's of any use within my work domain.
- EventFlow This is the magical framework used for CQRS and storing the entire state of the app as events
- Everything in-memory As everything is stored in-memory, it's quick to clone and run on your local environment
- ASP.NET Core 2.2 RazorPages An uncomplicated, WASM/JavaScript free UI layer, as the focus is on EventFlow.
The "business" is first line support for various Sites around the country.
Assuming that Operatives have been hired and Sites acquired:
- Response will raise Work when they are contacted by customers within those
Sites - Control will assign the Work to an
Operative Operativeswill then pick up this work and will result in one of two outcomes- When
Workis completed it is marked as completed - If the
Operativecannot complete work they abandon it. TheWorkis then back with Control to assign to anotherOperative
- When
The state of this prototype is not stored in a series of relational database tables. It is stored as a series of events in an event store.
As you interact with the prototype, the aggregate roots will emit events. If a business rule fails, such as not providing a forename when hiring a new operative, the event is not emitted. All events are persisted in an in-memory event store.
Meanwhile, read models are listening for domain events and persisting important information in a read model store. Queries can then refer to these read model stores. (rather than requerying the entire event store)
Ensure you have .NET Core 2.2 SDK installed on your machine
This prototype should not be used as an architectural reference, a good example of using EventFlow or DDD. I may refine it and grow it as I continue to learn about DDD.