One of the counter-arguments against Event-Sourcing you might heard about is that replaying events takes too much time.
Replaying 20 events for an aggregate is fast, 50 is ok, but 100 events and more become slow depending on the data of the events and the operations needed to replay them. A DDD rule of thumb says aggregates should be kept small. Keeping that in mind you should be fine with 50 events per aggregate in most cases.
3.4.1. But my aggregates record tons of events!
If aggregate reconstitution gets slow you can add an additional layer to the system which is capable of providing aggregate snapshots.
The snapshot feature is provided by the prooph/snapshotter package. Please refer to the docs of the package to learn more about it.
Also choose one of the
Prooph\EventStore\Snapshot\Adapter\Adapter for the
Prooph\EventStore\Snapshot\SnapshotStore to take snapshots.
Inject the snapshot store into an aggregate repository and the repository will use the snapshot store to speed up
Our example application proophessor-do contains a snapshotting tutorial.
Note: Snapshot store and all snapshot adapters ship with interop factories to ease set up.