title: Event Flow and EventSourcing
body: <p>I am trying to go over Eventflow to use on a POC after deciding I dont want to  create my own implementation of Event store and Event Hydration. Eventflow looks like a good option. I currently use Mediatr and with eventflow to keep things minimum I would use its Command Handling and Event Emits.</p>
  
  <p>I got stuck on one line in Documentation "In an event source system like EventFlow, aggregate root data are stored on events."</p>
  
  <p>Does this mean each time an event is stored in database/ event store it is also storing the current aggregate with its state?</p>
  
  <p>Why does it need to store the agrregate with event? Applying events when loading an aggregate should bring back the state , right?</p>
  
  <p>Also believe if it does so, the event itself is fairly light weight and the aggregate data storage is going to make it bulky.</p>
  
  <p>What purpose does it serve?</p>
  
  <p>Did I understand the statement incorrectly?</p>
  
  <p>links
  <a href="https://eventflow.readthedocs.io/Aggregates.html" rel="nofollow noreferrer">https://eventflow.readthedocs.io/Aggregates.html</a> 
  <a href="https://i.stack.imgur.com/aP3MJ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/aP3MJ.png" alt="enter image description here"></a>
  Thank you,</p>
  
  <p>Mar</p>