Event Sourcing with Svein Arne Ackenhausen
Yesterday, one of my teams and I participated in an Event Sourcing workshop with Svein Arne Ackenhausen , sharing his experiences going from traditional RDBMS state store architectures to event sourcing ones. This is my interpreted summary of the event. :-) Event Sourcing fits well within a a bounded context. Within this context, UIs can HTTP Post specific command DTOs to an endpoint which - Constructs a Command - Asks the Command to structurally validate itself (e.g. check a number range 1-10) - Send it to a Command Handler The Command Handler will - Invoke business rules to validate the Command (e.g. check if this user is allowed to invoke said command) - Load an Aggregate from an Event Source Repository (which in turn will construct the aggregate and might read an Event Store and replay all events onto it) - Send the Command to the Aggregate which, again, will validate the command against its state. If the Command is valid, the aggregate will send an event that describes