What is a Message Queue and When should you use Messaging Queue Systems Like RabbitMQ and Kafka

Message Queues system like RabbitMQ and Kafka are amazing technologies but when should you actually use a message queue? I discuss this in this video.

🏭 Software Architecture Videos

💾 Database Engineering Videos

🛰 Network Engineering Videos

🏰 Load Balancing and Proxies Videos

🐘 Postgres Videos

🚢Docker

🧮 Programming Pattern Videos

🛡 Web Security Videos

🦠 HTTP Videos

🐍 Python Videos

🔆 Javascript Videos

Support me on PayPal

Become a Patreon

Stay Awesome,
Hussein

[asadjivani]

What really exemplary about your videos is that you first explain the need and then explain the tools, keeping "necessity is the mother of invention" intact.

[karthikeyansrinivasan]

2020 is not all we learn a lot from your videos. Thanks for being there for us.

[dprophecyguy]

I am overwhelmed by the amount of the number of videos you post. I just found out your channel and it seems everything you post is essential for learning. So from today, I have decided to just watch any video you post as soon as possible to keep up with you.

[bubbyprime]

The way you explained this was extremely clear. I just landed a new job as a software engineer and the technology this company uses is Kafka. I took a messaging queue as something literal to actual messages. This makes a lot more sense now.

[monishkamble]

I was wading through "JMS" search results on YouTube and stumbled upon your video. And to my luck I found (a gem) somebody who explains concepts with such an enthusiasm.

This is the first time I am subscribing to a channel just by watching it's first video itself.

[Rxlochan]

You have a wonderful passion for Software Engineering. You just pulled me into this awesome ocean of software engineering. I'm super addicted to you channel. I've been watching all you videos continuously. Thank You🙏

[skylarkerzner]

Love your teaching style Hussein. I enjoy you always making it a fun experience -- it allows me to consume more educational content without feeling exhausted. I also really appreciate your commentary on opinions and habits of engineers around each video's topic, and your comparisons between different technologies -- it adds more context and useful information that you can't find in other educational content. Thank you for making these videos, and best wishes to you!

[cowsauce]

Not exactly what I was looking for, but the explanation was so clean and clear that I stuck around for the whole thing! Great video!

[tejsingh]

Best Youtube Channel for almost every concepts in backend

[kalmanjudin]

Nice! This method of consuming knowledge through a "virtual talk" is the next level. Entertainment and experience in one box!

[levonsarkisyan]

One of the most brilliantly simple explanations on Youtube. Thanks a lot, Hussein!

[KennethKJM]

thanks hussein for the video! i didnt understand message queues at first, but you literally covered all my questions in this video.

[prabinlamsal]

With the power of this one video, you have become one of my favourite people on the internet.

[manasyadav]

I always feel like first liking the video and then start watching it. This channel is the greatest i have seen so far

[realohh]

Have been learning Networking, backend and database from you on Udemy. It has been a great journey until now. Love your content

[psionski]

When you said “think whether you need a queue”, I actually did, and realized I don’t! I thought of a much simpler solution, thanks to that intro, LOL :D

[nelsonbravo]

Excellent video, We need more of this kind of videos help to decision making, identify and understanding the problem then analyze what tech/method can solve or minimize the problem.
also finally understood the difference of queue and pub/sub 10:52 .
thanks for share your knowledge.👍

[amitkumargouda]

Really appreciate how you explain complex topics in an easy way.

[atticus]

That answered lots of questions I had, and some I didnt have but should have had as well. Well done and thank you, subbed!

[henryowenz]

At the end you mentioned that the web server
should not process your request, it should just
respond. My question is, what are the other options
a developer should use to process request/data?
Should it be another server/service that the web
server then makes a API request to? Or maybe the
web server then connects to a message broker and
sends the data as a job to a server/service that just
handles processing the data for that specific job? I
know this video is from 2 years ago but the
information is timeless, thank you for all the content
you've created for the community!