CQS and CQRS: Command Query Responsibility Segregation
Vložit
- čas přidán 26. 07. 2024
- The CQS and CQRS design principles explained.
00:00 CQS: Command Query Separation
01:29 CQRS: Command Query Responsibility Segregation
2:10 Separating reads and writes
2:37 Scaling independently - Věda a technologie
bro you have the knack for this. Short, concise and really informative. Keep this format and keep more of them coming! Thanks.
I watched a 30-minute video but couldn't comprehend it. However, you were able to explain it to me in just 3 minutes, and I am grateful.
honestly, your are very underrated :/ Your are helping me alot with these videos! Thanks !
Thanks! Very glad I can help
Very underated channel, I hope it takes off
Here before 3k subs
Thanks! Glad you like the channel
What a wonderful channel!! I'm glad I found it, it's a fantastic resource to send to less technical colleagues about the concepts being used in the code.
Amazing video!! 👏
I love these videos! Keep them going!
Thanks for keeping it simple - much appreciated.
Insane 2nd video of the channel, keep them coming, I WANT MORE KNOWLEDGE
Please keep making these videos!
Yet another great video!!!
Please keep them coming !!!
Good videos (both of them). They are better than 80% of other YT software tutorials. I've subscribed. I WANT MORE!!!! More videos more videos more videos. 😃
Thank you for publishing another video today!!! DDD building blocks in less than 5 minutes - very useful and very clear!
Glad you like the videos :) I'll keep at it and hope you'll enjoy what I have planned!
holy shit thats what a clear explanation is!
Love your explanation thank you - I'm still on the fence about this paradigm. Again it feels like it was put together by some journeymen devs who were bored and felt they needed to invent something nobody asked for and probably another layer of bloat in microservice hell architecture. We developers often cite how complicated web development has become and its because of things like this.
Thanks! Glad you like it. I think in some cases you could argue that CRUD adds a layer of bloat to things that naturally have separate read and write models. But yes, using CQRS where it is not a good fit just unnecessarily complicates things
Thanks for the video, wish you more subscribers!
Simple, But very informative. Thanks
Loved the format
love these videos
Brilliant video, informative and concise. I would suggest Unit Of Work video. I really appreciate your efforts. 👍
Thank you for the suggestion! I do plan on going into that sort of stuff in the next few videos :)
This is fine for atomic streams of operations that don't conflict received in order. Like 80% of website style transaction. However it does NOT scale horizontally. It provides, no, it refuses basic concurrency monitor controls and basics like "Test and set". Splitting a "Dequeue" operation into 2 concurrent/ordered operations leaves you wide open to race conditions, dead locks and I cannot see how this scales horizontally to accomodate increasing loads.
You should make more videos...
please avoid the background music...it's irritating.
Visual Description is very pleasant. Keep it coming
Glad you enjoyed the visuals! In my later videos the music is quieter and filtered, which is hopefully less irritating. Thanks for your feedback
You should improve your video release schedule :)
I'll definitely try to be quicker for the next one :D
This background music is of very poor quality, looks like it was recompressed multiple times. Please consider removing it. Otherwise great content. Subscribed.
Thanks for your feedback! I don't intend to totally remove the music, but I have been working on making it sit better, keeping the rhythm and flow without distracting from the main content. Hopefully you'll prefer it in future videos
I have trouble hearing your voice over it
Pls avoid background music
This is how you create slow programs