Podcast.init

Event Sourcing with John Bywater – Episode 131

Oct 15 '17

Summary

The way that your application handles data and the way that it is represented in your database don’t always match, leading to a lot of brittle abstractions to reconcile the two. In order to reduce that friction, instead of overwriting the state of your application on every change you can log all of the events that take place and then render the current state from that sequence of events. John Bywater joins me this week to discuss his work on the Event Sourcing library, why you might want to use it in your applications, and how it can change the way that you think about your data.

Preface

Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
I would like to thank everyone who supports the show on Patreon. Your contributions help to make the show sustainable.
When you’re ready to launch your next project you’ll need somewhere to deploy it. Check out Linode at podastinit.com/linode and get a $20 credit to try out their fast and reliable Linux virtual servers for running your awesome app. And now you can deliver your work to your users even faster with the newly upgraded 200 GBit network in all of their datacenters.
If you’re tired of cobbling together your deployment pipeline then it’s time to try out GoCD, the open source continuous delivery platform built by the people at ThoughtWorks who wrote the book about it. With GoCD you get complete visibility into the life-cycle of your software from one location. To download it now go to podcatinit.com/gocd. Professional support and enterprise plugins are available for added piece of mind.
Visit the site to subscribe to the show, sign up for the newsletter, and read the show notes. And if you have any questions, comments, or suggestions I would love to hear them. You can reach me on Twitter at @Podcast__init__ or email hosts@podcastinit.com
To help other people find the show please leave a review on iTunes, or Google Play Music, tell your friends and co-workers, and share it on social media.
Your host as usual is Tobias Macey and today I’m interviewing John Bywater about event sourcing, an architectural approach to make your data layer easier to scale and maintain.

Interview

Introductions
How did you get introduced to Python?
Can you start by describing the concept of event sourcing and the benefits that it provides?
What is the event sourcing library and what was your reason for starting it?
What are some of the reasons that someone might not want to implement an event sourcing approach in their persistence layer?
Given that you are storing a record for each event that occurs on a domain object, how does that affect the amount of storage necessary to support an event sourced application?
What is the impact on performance and latency from an end user perspective when the application is using event sourcing to render the current state of the system?
What does the internal architecture and design of your library look like and how has that evolved over time?
In the case where events are delivered out of order, how can you ensure that the present view of an object is reflected accurately?
For someone who wants to incorporate an event sourcing design into an existing application, how would they do that?
How do you manage schema changes in your domain model when you need to reconstruct present state from the beginning of an objects event sequence?
What are some of the most interesting uses of event sourcing that you have seen?
What are some of the features or improvements that you have planned for the future of you event sourcing library?