engine v0.1.2 Engine.Aggregate.Container
This module encapsulates the Database side-efects over the aggregate Container. So the data structure from server state (that contains the aggregate data structure) and rehydrate it with data, from snapshots and events. Easier to test, debug and mantain :) . So we focus only on retrieving and persisting data here, creating new pids, and other decisions should be make by the server, repository and router.
Yes, I know that this Container is the server’s state, but the word state is too wide, Container is better because in relation of the Aggregate data structure, this server’s state is holding another datastructure plus some metadata (uuid, etc.). If you come from Enterprise Java Beans, you will love this Container, specially that it can take 18 microseconds to start some millions of them ;)
Note that when we snapshot, we save the server state, that contains the aggregate data structure, and we need to replay the remaining events only from the data structure.
Summary
Functions
returns [first, last] positions of the appended events
returns [first, last] positions of the appended events
returns [first, last] positions of the appended events
returns [first, last] positions of the appended events
Types
Functions
returns [first, last] positions of the appended events
returns [first, last] positions of the appended events