Over a long period of changes to any and all Aggregate instances, doesn’t the playback of hundreds, thousands, or even millions of Events cause serious latency and overhead in processing the model? At least for some of the higher-traffic models that would most certainly be the case. To avoid this bottleneck we can apply an optimization that uses Aggregate state snapshots. A process is developed to produce, in the background, a snapshot of the Aggregate’s in-memory state at a specific point in Event Store history. To do this, the Aggregate is loaded into memory using all previous Events to the
...more
