FUNCTIONAL FOUNDATION OF EVENT SOURCED APPLICATION
summary
Functional programming claims handle failure, asynchronicity, concurrency and IO while keeping purity, and demonstrates it by modeling CQRS/ES with three concrete functions: command -> events, event handler: state update and the derived apply command to aggregate function. Effects are explicit as an F that can be Future, Try, Option or Identity. Aggregates act as accumulators folded from event history (example: a natural-number model with thousands of events) and the talk flags practical limits like reading half a million events into memory.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:16What is CORS/ES?
- 4:25Two basic functions and a derived one
- 5:11A Command can be rejected
- 6:14In the begining there is None
- 7:52An Aggregate aggregates its past
- 13:08Effects
- 15:40Backend
related talks
45mFunctional Programming in the Large - Status and Perspective
52mEvent-driven vs event sourcing: what's really the difference?
46mPractical Functional Programming in C++
01h 06mDesigning Applications with Functional Programming Constructs
56mEvents on the outside, on the inside and at the core
36mCurrent state vs. (eve)nt sourcing
52mEvent Sourced Transformation in Financial Systems
49mCQRS and Event Sourcing explained