Popularity of event sourcing among Python developers seems to be moderate but growing. It can be seen as an enterprise architectural pattern, not worth considering in "smaller" applications.

The goal of this talk is to spread the knowledge about what the event sourcing is, what hides behind the corner of an initial implementation and to help decide whether your code will benefit from it enough to be worth the cost. As any other tool, event sourcing is not a silver bullet and it won't be portrayed as such - it has its drawbacks and introduces a fair amount of complexity.

Only small amount of code will be shown during the talk - and more to visualise the idea than to prescribe a specific implementation. These and all other topics will be backed by over three years of practice in designing, developing and running applications equipped with event-sourcing-based storage under production traffic - which, I believe, gave us enough real-life examples to showcase ES' strong sides and associated stumbling blocks.

Last note: while these are strongly related topics, I will be only briefly mentioning DDD, CQRS and EDA and - ES will be the main focus.

Jacek Kołodziej

Affiliation: Growbots

Python back end developer at Growbots. Aspires to be A Programmer - that'd be a lot to unpack to describe it, let's talk. :)

Photographs, runs, wanders from one concert to another and from one hill to another, too. Plays drums occasionally.

visit the speaker at: Twitter • Github • Homepage