A deep-dive podcast episode covering event sourcing as an architectural pattern in Python. Chris May explains how event sourcing stores every state change as an immutable event rather than mutating rows, contrasting it with CRUD. Topics include the eventsourcing Python library by John Bywater, CQRS and read models for performance, event versioning strategies (upcasters, defaults, the nuclear option), vertical slice architecture, and the 'closing the books' technique for managing stream length. The episode also covers when to use event sourcing (look for 'status' columns), when not to (simple forms-over-data apps), real-world wins like backfilling analytics and compliance audit trails, and why event-sourced codebases are particularly well-suited for AI-assisted coding with tools like Claude Code.
