Event Sourcing 101: Command Query Responsibility Segregation (CQRS)

why is that stupid name? why not: spoon, noodle, cup, keyboard (four random things on my table)? I am telling you: two years from now you will have DRST to replace CQRS arguing how terrible CQRS is comparing to DRST. I am not jump on to something knowing it's going to be garbage in two years.

What is so much hype? We store events as history and only INSERT for better performance. insertion is suitable in normalized tables. Query portion is easier in denormalized format as a single select * form denormalized. The update from normalized -> denormalized happens only 1 time with kafka queues in the background. I don't think there is more to it. Thats how I would explain 1 line

it is very interesting to understand this paradigm because help us not to create a complexity where do not need

Clear and objective explanation. Thank you.

The hand gesture is distracting and she talks too fast.

The most clear explanations on CQRS & event sourcing I've ever watched/read, thank you!

What would happend if i have to change the event format and we have a lot of events gathered in the log?Thank you!

So the system will eventually "inconsistent" as said read will not b possible right after "write", performance or segregation tradeoffs with data inconsistentcy... Apart from this why I would b interested from real world usecase POV that if user first add T shirt then delete T-shirt n add Pants to the cart n add one more Shirt n delete added Pants n added T-shirt again...ok we are writing these events to eventlog just to have record where user started???why I would b interested what was the system state at the time when this user started shopping??? What I want to achieve from that!??

Short and clear! Very good

Great explanation, thanks

What is the benefit of CQRS?

Much needed right now
Thank you 🙏