Start describing the User state. Modeling it as snapshots.
Code cleanup.
Remove unused actor factories. Now superceded by the actor provider.
Start implementing user balance REST request.
The persistence database schema as a configurable option
All Aquarium events have a client defined unique id
Renames to more meaningfull names
Implementation of the EventStore interface in the Mongo driver
Compilation fixes
Use the event store in the event processor to persist resource events
View revisions
Also available in: Atom