yeahh this is an amazing way for proficient programmers to learn more about the architecture behind larger software systems! Thanks!
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.
How does he do it How does he have everything im trying to teach myself lined up I cant stress enough how these vids crystallized so many of the concepts I've been studying and putting into practice in personal projects. Literally saving lives out here
Great explanation❤. Can you make one video explaining how to implement it?
You just earned a sub! Awesome explanation mate
this videos are gold!
exceptional well explained!
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.
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!
first time get to know with event sourcing and CQRS, some one please explain to me what is DDD's responsibility, if we combine 3 of those in microservice
P r o m o s m
@ciberman