Future is a thing of the past
summary
An online board‑game shop gets built as a running example to prove event sourcing and domain events capture business facts, not CRUD; the system appends events, projects read models, and replays history to time‑travel. Implementation details: PHP named constructors, board game stock was replenished events, storage in event store (MySQL) or GetEventStore, projections for lists, and process managers for long workflows. Real deployments hit a few thousand events; MySQL handles up to two million rows so it works in practice.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:24an online board game shop
- 0:37selling a board game
- 1:39Board Game Stock Was Replenished
- 6:03the payload
- 6:18keep an eye out for the amount of properties
- 7:45Event Sourcing in a nutshell
- 7:56instead of modifying columns in rows
- 9:20implicit information
- 11:03lifecycle of a domain concept
- 23:00how do we create a projection?
- 33:09project same data to multiple things
- 33:59have the best audit log ... ever
- 34:25fix database schema bugs
related talks
33mPut Verbs in your database
40mEvent Sourcing with Laravel
32mEvent Sourcing in Laravel with EventSauce
28mDaniel Coulbourne :: Flip the Switch Slowly
24mTime Driven Development
44mBuilding a complex product while scaling a team and a business on Laravel
40mEngineering Complex Applications with Laravel 4
20mhow to make the management of a league system less traumatic