"Every change captured as an immutable event you can replay, instead of a single mutating row that quietly forgets its own history. That's event sourcing, and Chris May is back on Talk Python, fresh off our Datastar panel, to walk us through what it actually looks like in Python."
"We'll cover the core patterns, the libraries to reach for, when not to use it, and why event sourcing turns out to be a surprisingly good fit for AI-assisted coding. Watch the live stream version Episode Deep Dive Guest Introduction and Background"
"This episode is architecture-heavy, so it helps to be comfortable with the basics of databases, CRUD operations (create, read, update, delete), and Python classes before listening. You don't need to know any specific framework, but a passing familiarity with an ORM (like Django's ORM or SQLAlchemy) will make the read-model and migration discussion click faster."
Event sourcing records each change as an immutable event rather than overwriting a single mutable row. State is derived by replaying events to build current results, often using read models that are updated from the event stream. The approach emphasizes core patterns, suitable libraries in Python, and practical guidance on when event sourcing is a good fit and when it is not. Familiarity with databases, CRUD concepts, Python classes, ORMs, caching, JSON serialization, and APIs helps listeners follow discussions about read models and migrations. The model’s replayable history can align well with AI-assisted coding by providing durable context for reconstruction and reasoning over changes.
Read at Talkpython
Unable to calculate read time
Collection
[
|
...
]