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!
Excellent! I've never really worked on any systems where Eventual Consistency is a thing... and I've, obviously, heard the term bandied about a lot... but never really known how it works.... until now! :)
For our new system I actually implemented an event-sourced system backed by SQL using efcore; it's typed, uses automatic JSON versioning and upgrade-on-read, as well as a strongly-consistent projections system where the projection state goes in the same transaction as the event append. Performance has actually been pretty great, and the way it makes rearranging the read model as requirements change has been absolutely amazing, I don't think I'd want to go back to a regular ORM.
Best explanation with short videos. I really like it. Understood well about DDD.. Please post a video related AWS migration from off-premises to ON premises for legacy application ex: Java application
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!
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
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.
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
yeahh this is an amazing way for proficient programmers to learn more about the architecture behind larger software systems! Thanks!
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!
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!
Excellent! I've never really worked on any systems where Eventual Consistency is a thing... and I've, obviously, heard the term bandied about a lot... but never really known how it works.... until now! :)
Really great content, best explenation I could find out there, and makes it very clear
For our new system I actually implemented an event-sourced system backed by SQL using efcore; it's typed, uses automatic JSON versioning and upgrade-on-read, as well as a strongly-consistent projections system where the projection state goes in the same transaction as the event append. Performance has actually been pretty great, and the way it makes rearranging the read model as requirements change has been absolutely amazing, I don't think I'd want to go back to a regular ORM.
Best explanation with short videos. I really like it. Understood well about DDD.. Please post a video related AWS migration from off-premises to ON premises for legacy application ex: Java application
Great explanation❤. Can you make one video explaining how to implement it?
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 :)
I'm addicted to these! Keep it up!
You just earned a sub! Awesome explanation mate
Simply asesome! Thanks you!
You deserve lot more subscribers!
Great video! Thanks for sharing!
exceptional well explained!
Awesome content! Thank you
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!
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
this videos are gold!
Thank you man may rate 10/10
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.
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
@@drawingboxes Yea, the events are the truth not the snapshot. Gotcha!
what books do you recommend to read further?
P r o m o s m