**Summary** *Background:* - A message queue will help in *decoupling* two components (e.g. checkout and inventory) - Components can *scale* based on demand - Queue sits on a different machine and can offload some of the work of components and make it more *performant* *RabbitMQ:* - It is based on the AMQP message model. - Producer produces the message to exchange instead directly to the queue. - exchange can be connected to many queues - Queues are connected to the consumer by a binding key - Flexibility is a large part of the model - Different types of exchange - Fanout - the message is duplicated to all the queues - Routing Key - sends to queue matching the exact binding key - Topic - matches based on topic e.g. message is sent from routing key "ship.shoes" and binding key "ship.any" - Header - messages are moved through the system-based header - Default (specific to RabbitMQ not part of AMQP) - matches the routing key with the name of the queue e.g. "inv" routing key matches the "inv" queue name. - the consumer has the control, not the message broker, they define the message metadata - it is cloud-friendly - easy to get started - can be deployed in a container e.g. docker - can run on the cluster (fault-tolerant, highly available and high throughput) - It has good library support in many languages. - It has good security supports FASL, LDAP and TLS. - It supports message acknowledgements - Good management and plugins.
I wish 10% of technical videos of this kind were as good as this one. Content, pace, delivery, and relevance were all exemplary. No nonsense "X in 100 seconds" approach. Good to see there are still great teachers who only need a board to draw on to explain things well and effectively. Thank you, you have a new subscriber.
I wanted to learn the basics of RabbitMQ and this video is just great for that. I value the fact that the instructor went over the basics of the messaging queue and the underling aspects such as the exchange and how that relates to the queues that are named with a tag. Other videos talk about asynchronous communications and then jump into a code example. You can explain the concepts of something without going immediately into one of many implementations. Thanks.
Lol, Initially I thought the same. But that's called a "Lightboard". They write on a glass and the Video is then mirrored. Check these out: th-cam.com/video/VhtEmcNWtyg/w-d-xo.html th-cam.com/video/wCOuu0-o5YI/w-d-xo.html
This is a great and concise source for getting to know RabbitMQ but I'm more impressed by the fact that she can inversely on a transparent whiteboard so that a camera on the other side can read it.
Thanks for the video. A comparison of message queues and other publish/subscribe systems (e.g. Apache kafka) would be very helpful for beginners like me.
She proposed three benefits of RabbitMQ decouple scalable performant In 2023 when I can deploy containers to something like AWS ECS, how much of and issue is “scalability” and “performance”?
Thanks, Whitney and the entire production team. I really like these videos that explain the crux of the stuff in less time. I'm interested in learning more about this. Can you recommend books or any other sufficiently complete resource(s)?
I was monitoring for some time MQ servers years back, you know alert, admin log in, check services running, restart them if are down, but I was now-years old when I learned how MQ works, back then it was "just another app that had to stay up".
Hello, I would liketo ask if it is a good practice to have a message consumer in frontend web app? I suppose no, because in this way the rabbitmq server's credentials could be seen by everyone and so anyone could consume your information as well, right?
Thank you very much Whitney. I enjoyed this video very much. It is very informative and has all the relevant details in 10 minutes. Very concise and well explained.
Awesome. Now I have a great RabbitMQ intro-video to hand-out to my team ;-) Just one tiny thing: The topic part could confuse some people since the usage of "wildcards" is not mentioned (only implicitly). Or maybe I have overseen something? Thank you for the great work!
Is RabbitMQ really so cloud friendly. Surely it needs persistent volumes to hold onto all those messages if deployed on Kubernetes or Docker Swarm? I would hope those messages are not persisted within a local docker container file system, as containers needed to be treated like cattle. We need to b assured that no data is lost even if there are container and pod runtime failures.
So do you write reverse? Or some sort of video processing magic? I am trying to figure out if I want to make such videos for some of the kids I teach, how can I do it?
I imagine all you need is a transparent board in between the camera and yourself, and you write normally, then in post-production, you flip the video horizontally such that it will appear you are left-handed when you are right-handed for example (as is the case in this video).
IBM's transparent chalkboard lecture are always the best.
she really is writing mirrored letters? 😶
She is right handed btw 🤷
@@Suraj-tz3oq thats insane
The board is actually towards themselves. So in the end they mirror the screen.
Yeah transparent. Even the writing is transparent. Can't see anything.
**Summary**
*Background:*
- A message queue will help in *decoupling* two components (e.g. checkout and inventory)
- Components can *scale* based on demand
- Queue sits on a different machine and can offload some of the work of components and make it more *performant*
*RabbitMQ:*
- It is based on the AMQP message model.
- Producer produces the message to exchange instead directly to the queue.
- exchange can be connected to many queues
- Queues are connected to the consumer by a binding key
- Flexibility is a large part of the model
- Different types of exchange
- Fanout
- the message is duplicated to all the queues
- Routing Key
- sends to queue matching the exact binding key
- Topic
- matches based on topic e.g. message is sent from routing key "ship.shoes" and binding key "ship.any"
- Header
- messages are moved through the system-based header
- Default (specific to RabbitMQ not part of AMQP)
- matches the routing key with the name of the queue e.g. "inv" routing key matches the "inv" queue name.
- the consumer has the control, not the message broker, they define the message metadata
- it is cloud-friendly
- easy to get started
- can be deployed in a container e.g. docker
- can run on the cluster (fault-tolerant, highly available and high throughput)
- It has good library support in many languages.
- It has good security supports FASL, LDAP and TLS.
- It supports message acknowledgements
- Good management and plugins.
Are Headers and Labels the same thing?
best 10min ecture on RAbbitMQ . easy to understand and straight to the point. loved it.
I wish 10% of technical videos of this kind were as good as this one. Content, pace, delivery, and relevance were all exemplary. No nonsense "X in 100 seconds" approach. Good to see there are still great teachers who only need a board to draw on to explain things well and effectively. Thank you, you have a new subscriber.
☆彡(ノ^^)ノ thank you!
the calmness when explaining is appreciated
Very well explained. IBM lectures are quite comprehensive.
The explanation is so simplified that even a non-IT person will grasp the whole concept of message handling. Well done!!
This is one of the best explanation of general messaging systems & RabbitMQ so far! Great job!
Finally I've found a video that well explains message queues
great example of excellent left handed minds and artists, both artistic & technical, righting back-to-front.
I wanted to learn the basics of RabbitMQ and this video is just great for that. I value the fact that the instructor went over the basics of the messaging queue and the underling aspects such as the exchange and how that relates to the queues that are named with a tag. Other videos talk about asynchronous communications and then jump into a code example. You can explain the concepts of something without going immediately into one of many implementations. Thanks.
Glad it was helpful!
Whitney needs to be in the Guinness book of record for her excellent teaching skills. well articulated
Very good explanation. To understand the necessity to use a message broker in a microservice enviroment and in a scalable enviroment
I like this style of teaching, old school with a modern chalkboard. Well done!
This is a really concise, and well explained introduction to RabbitMQ. Thank you Whitney!
Nice 10 min intro for RabbitMQ video to share with team.
This is perfect! I didnt even know what a message broker was and after this, I have something solid to start with. Thank you Whitney!
You're welcome, thanks for watching! 👍
awesome presentation. Today I got it completely, my confusion was about how it's handled lots of messages, but now it got resolved. Thanks, Whitney
My first thought to this was - wow, she's really good at writing mirrored text!
Whitney makes it sound so easy.
Whitney your hard work reflects in the content and explanation. I wish I could have you as my cloud trainer
That fact that she is writing inverted so fast is mind-blowing.😄
Or they just flip the entire video afterward
my favorite channel. always come here to learning new stuff
I cant believe how casual she's writing backwards .. well explained ! Thx
Lol, Initially I thought the same. But that's called a "Lightboard". They write on a glass and the Video is then mirrored. Check these out:
th-cam.com/video/VhtEmcNWtyg/w-d-xo.html
th-cam.com/video/wCOuu0-o5YI/w-d-xo.html
She is not writing backward. She is using lightboard.
Really appreciate use of different colors for better understanding...thank you for the video👌
This is great overview. As I have got to know. working on that is not east at all.
That is some serious spatial awareness. Good job for writing mirrored and backward. Great content.
lol they just mirror the video :p
Just the right level of detail for refreshing/preparing for an interview, thanks!
Glad this was helpful, good luck with your interview! 🤞 💪
thanks for the concise explanation. been confused about this message queueing system for a while.
One of the best explanations about RabbitMQ ever!
Concise and well explained. Thanks
very useful info within 10min. thank you!
This is a great and concise source for getting to know RabbitMQ but I'm more impressed by the fact that she can inversely on a transparent whiteboard so that a camera on the other side can read it.
These videos always look so cool
I don’t know who had the idea to design them that way but it was genius, they always stand out
#Explain Like I’m 5! Awesome explaination Whitney.
a valuable 10 mins video. thanks for sharing
Thank you for the very clear and concise introduction!
very well explained , thanks to IBM and Whitney for enabling and explaining this good
I'm mesmerized more on how easily she writes backwards from her perspective.
I thought she just wrote normally and they flipped the video
This is very concise and amazing. I love the video. Never knew when I got to the end of it. 😄. Thank you to the entire production team.
Hey there! Thanks a lot for your feedback, glad you enjoyed it! 😃
This was one of the best educational video I have ever seen. thanks!
Thank you and can't help thinking how this chalkboard works，does the demonstrator need to write reversely？
Very good explanation👌👌
Very good explanation
concise, to the point explaination!! awesome. loved it :)
really well explained !!
When I seriously listening to this video I thought mouse is moving around my room.thank u for clear explanation
oh my god! I was just searching for rabbitMq in IBM this morning.
Thanks for the video. A comparison of message queues and other publish/subscribe systems (e.g. Apache kafka) would be very helpful for beginners like me.
Thanks for the feedback, let us think about it. Stay tuned! 🙂
Thanks a lot! Very helpful video 👌
love this lecture...
Finally good and full explanation
In which scenarios, use of rabbitMQ is necessary? Should call to other api should be done via rabbitMQ or just direct http request without the broker?
How the heck did you learn to write backwards - nicely done 😊
Good explanation with positive vibes that cached me. Thanks
Love this explanation and now have better understanding of producer/sub model. Thank you.
Nice explanation, nice presentation. I like how these whiteboard talks are evolving -- they now have animations -- cool.
Awesome overview.
please how are these kinds of video presentations made, I really love them
Excellent overview! Thank you, Whitney.
Crystal Clear. Thank you.
Fantastic explanation, even for a non-programmer like myself
We're glad you found it useful and easy to understand, Adam! 👍
She proposed three benefits of RabbitMQ
decouple
scalable
performant
In 2023 when I can deploy containers to something like AWS ECS, how much of and issue is “scalability” and “performance”?
Great explained,
Can you please also make video on "jenkins" ?
It will be very helpful
Thanks Akash! We've already touched the subject of Jenkins in this video ➡️ ibm.co/3I2ulZa
Is she writing backwards or is there some tech sorting that out? Mind Blown.
Hi
Can you please make a video on difference between kafka and rabbitMQ ?
Thanks, Whitney and the entire production team. I really like these videos that explain the crux of the stuff in less time. I'm interested in learning more about this. Can you recommend books or any other sufficiently complete resource(s)?
Excellent overview Madam. Thank you very much.
great overview
Very concise tutorial, thank you.
You are 🥲 lifesaver
I was monitoring for some time MQ servers years back, you know alert, admin log in, check services running, restart them if are down, but I was now-years old when I learned how MQ works, back then it was "just another app that had to stay up".
This is really good
This is really great
Innovative old school teaching.
Awesome job
Super clear explanation! Thanks!!
Excellent explanation. Really precise and concise.
Hello, I would liketo ask if it is a good practice to have a message consumer in frontend web app?
I suppose no, because in this way the rabbitmq server's credentials could be seen by everyone and so anyone could consume your information as well, right?
perfect explanation! thanks for creating this!
HHHM! Nice teaching. I can enroll in all her courses.
Well explained
This is Great 💯
Thank you very much Whitney. I enjoyed this video very much. It is very informative and has all the relevant details in 10 minutes. Very concise and well explained.
Great explanation!
Wow!! Such a nice explanation. I want to learn every topic from you. Thank you for such a great video.
Awesome. Now I have a great RabbitMQ intro-video to hand-out to my team ;-) Just one tiny thing: The topic part could confuse some people since the usage of "wildcards" is not mentioned (only implicitly). Or maybe I have overseen something? Thank you for the great work!
That was a great video, have little knowledge of MQTT. This helped.
I love this explanation , thank you for saving me lot of time
You're welcome, Santhosh, glad you found it useful! 😀
Is RabbitMQ really so cloud friendly. Surely it needs persistent volumes to hold onto all those messages if deployed on Kubernetes or Docker Swarm? I would hope those messages are not persisted within a local docker container file system, as containers needed to be treated like cattle. We need to b assured that no data is lost even if there are container and pod runtime failures.
Thanks for this fantastic explanation of RabbitMQ!
Thank you!!
Thanks for the video .. Info is very clear and crisp
Thanks for watching! 🙌
Thanks: nice way of presentation. Thorough and concise.
Thanks you!
So do you write reverse? Or some sort of video processing magic? I am trying to figure out if I want to make such videos for some of the kids I teach, how can I do it?
I imagine all you need is a transparent board in between the camera and yourself, and you write normally, then in post-production, you flip the video horizontally such that it will appear you are left-handed when you are right-handed for example (as is the case in this video).
Notice she writes with her left hand. Most likely, the video was horizontally flipped.
Outstanding! Really loved this, great explanation :)
thank you, it's really concise and easy to understand
"let's travel back in times to the days of monolith architecture"
Aah, yes.. earlier this morning.
Ha!
Wow. Very easy to understand, incredible job.