mspnp/cqrs-journey-code — pull request #160 by jdom (2012-04-17 02:40:59+00:00)
Title: #141 Migration to event sourcing

Migrated registration BC to use event sourcing for storing its own aggregates
Due to the increasing number of integration events being published, it made sense to do this migration, and also thinking about versioning after v1.

Right now, it uses an EXTREMELY basic event store based on SQL, which does not do any transactions with the event bus, nor checks for event versions being incremental, etc. If someone else can take up this work and replace the entire infrastructure for event sourcing, be my guest.

Also, SeatsAvailability aggregate could produce a lot of events. It feels like it needs some (in memory?) caching or snapshot mechanism.