Event Sourcing Explained

What is Event Sourcing? Is it anything to do with CQRS and DDD? We explain the pros and cons compared to traditionally updating the current state in a database. We cover trade-offs with Eventual Consistency, problems with concurrency, and options to solve those with optimistic concurrency techniques.
0:00 Intro
0:40 Deleting
0:57 Analytics & Metrics
1:23 Concurrency
2:24 Calculating State
3:26 Eventual Consistency
4:29 CQRS & DDD

[@jenreiss3107]

yeahh this is an amazing way for proficient programmers to learn more about the architecture behind larger software systems! Thanks!

[@urldog8876]

I'm addicted to these! Keep it up!

[@Zainjerr]

You just earned a sub! Awesome explanation mate

[@Legion739]

Really great content, best explenation I could find out there, and makes it very clear

[@douglasemsantos]

Great video! Thanks for sharing!

[@fraineri]

I just discover your channel today and the content is awesome! I would love to see what other topics you will talk about in the future. Keep it up!

[@drawingboxes]

Thank you! I'm glad you like it. I'm working on some videos in the agile and DevOps areas atm, and I've got another idea for content I hope to experiment with in the new few weeks - watch this space!

[@gianlucalocri]

Simply asesome! Thanks you! You deserve lot more subscribers!

[@fredimachadonet]

Awesome content! Thank you

[@TheHawkeyede]

exceptional well explained!

[@CristianMolina]

this videos are gold!

[@JustCode512]

Thank you man may rate 10/10

[@jaimalad2902]

Great explanation❤. Can you make one video explaining how to implement it?

[@drawingboxes]

Thanks! I'm not sure how to make a 'boxes and arrows' style video of that, but perhaps I can write up a post and make an example project soon :)

[@nadzhafox]

Very interesting to know how implements events sourcing? Using query manager for events? Save event in db after creation or after consuming? From front end dev I remember saga pattern for complex calculation of events, mb something similar using in backend system; P.S. great video as always; You helping me moving forward in my career!

[@drawingboxes]

Glad you're enjoying the videos! There's no single correct way to implement event sourcing, it's all trade offs, so its worth thinking about whether you'd prefer consistency, performance, or resiliency

[@sultan_of_oop]

what books do you recommend to read further?

[@b03tz]

Just a simple question: but what if you store the event index together with the snapshot. Then you can read the snapshot + events from that index forward and apply them to the snapshot to get the current truth. You would only have to read a few events then, just everything from the snapshot upwards and apply them.

[@drawingboxes]

Yes, absolutely, great thinking! You could store a snapshot at regular intervals and just replay the events that have happened since that snapshot was taken. Just as long as the snapshots could all be destroyed and re-built from the full list of events if needed

[@b03tz]

@@drawingboxes Yea, the events are the truth not the snapshot. Gotcha!

[@teda7365]

P r o m o s m