Sorry for the cut off intro, I don't know why that happened. What I said was "I get a question a lot that I thought was important to cover..."

The producer-consumer design pattern is probably one of the most important patterns in CS you can learn. It has a so many applications.

I subscribed quite some time ago but I don't watch your videos often (most of them aren't exactly what I need as I don't plan to become a dev, I just want to have some light dev competency aside to make it very easy to actually talk and work with development teams, as well as being able to build my own personal projects). Everytime I watch one of your videos I'm just astounded by your delivery. A huge amount of information packed together in a very clear and synthetic manner. Most people doing explanation videos will have a 2/3mn intro planting useless context, and then rant during 2 minutes on each and every concept, and what could be a 30s video turns out to be a 12mn one. You on the other hand make what could be a 10mn video into a 10mn video, perfectly delivered. Thanks for your work.

Perfect high level explainations of IT stacks which every software Engineer should know. Great video !

I just found your channel today and it’s like astoundingly great

The amount of information in this video is amazing, Thank you so much

Love your content. You’re one of those channels that I instantly turned notifications on for because I genuinely learn something invaluable in every video, thanks man.

This overview was exactly what I was looking for! Thanks a lot, Engineer Man!

Thanks for the video! I think Caching systems like Redis would be good to include

Great resource tying everything together

hmm... i think the protocol section could be re-done. The OSI layers are blurred. Seems to infer that tcp is separate from http and websockets.

Damn.....quite some infos you gave there....good job!

Super insightful!

I think that many people in the programming sphere including me will find this video very useful and helpful for getting a perspective for building software

Thank u so much man , thats super helpfull for me ❤️❤️❤️❤️

Could you do another video walking through how each of these contribute to the end product from the perspective of a user? I often find it difficult to understand how each piece contributes to the user experience. IE, how are databases updated on the backend if the input isn't well-defined? How agnostic are various software to operating systems?

I'll mention for people reading here, HTTP is actually a protocol wrapped around TCP, so HTTP is TCP, just a specific usage of TCP. Same with Websockets actually, still just TCP, but a different protocol wrapped around TCP.

I think it's important to call out that a lot of the devices listed in this video and the ways in which they are categorized are artifacts of cultural norms, not technical constraints.

This could not have come at a better time! Love your videos man

1:00 a part of my school services runs on Microsoft IIS. I wonder if that's what makes it be so laggy at times...

But how do you learn how to do these stuff? Not to program in this stuff but how to do them? How do i start making TCP or the web for example? I have no clue on this, would a CS degree help with that or you need something else for learning this?

I’m confused with UDP. Whst do you mean by it doesn’t matter if it’s received or not?

nice

My only comment is a lot of java frontends these days are done in javafx and not swing though swing still works fine