Event Sourcing made Simple
summary
Shows a concrete claim: Event Sourcing runs on a Rails monolith with ActiveRecord and SQL using a 150 lines of code framework. It records events with metadata, uses pessimistic locking, sorts by created_at and id, and has reactors (sync or async) for side effects. Kickstarter’s Drip runs 15 aggregates, 135 event types, 60 reactors, about 100,000 aggregates and 500,000 events. Replays restore lost records, backfill new columns, and forward events to Redshift/StatsD/Grafana for reporting.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:05record the completion date
- 1:39create a race migration
- 2:32add some event tracking
- 3:21create an activity item
- 15:39setting the completed attribute
- 17:58associate a reactor with an event
- 19:07create an activity entry in the database
- 31:35document your events
related talks
32mEvent Sourcing in Laravel
48mEvent Sourcing - what could possibly go wrong?
52mEvent Sourcing for the Cloud Developer
40mEvent Sourcing: the good, the bad and the complicated
44mEvent Sourcing - You are doing it wrong
52mEvent Sourcing – the what, why & how
49mCQRS and Event Sourcing explained
24mHow To Combine Event Sourcing Architecture In Your Node.js Server