the state of an application. It is a design pattern that stores state changes as a sequence of events, allowing the state to be reconstructed at any time.
consumer, consumer should receive anything • Establish naming (v1, v2) • Make consumer match the version • Write a handler between EventStore and Consumers
Suggested trips • Time to load • Time to unload • Vehicle type/capacity • Oil variants • Road costs • Routes • US enabled • Cost of trip • Best ROI • Negotiate
Change Aggregates Event is the starting point Events Are Immutable Event should have all data (or versioning) Projections come from events One flow per GenServer (account, order, etc) Managers Must Not Read from Projections