What is a MESSAGE QUEUE and Where is it used?
Вставка
- Опубліковано 10 чер 2024
- Messaging Queues are widely used in asynchronous systems. Message processing in an asynchronous fashion allows the client to relieve itself from waiting for a task to complete and, hence, can do other jobs during that time. It also allows a server to process its jobs in the order it wants to.
Messaging Queues provide useful features such as persistence, routing, and task management. We will be discussing the benefits of a message queue in future videos.
A system having a message queue can move to higher-level requirements while abstracting implementation details of message delivery and event handling to the messaging queue.
The 'queue' is just a name for this data structure. In practice, it could be storing messages using any policy. Some examples of message queues are Kafka and RabbitMQ. They are widely used for various purposes, such as command query request segregation (CQRS) and event sourcing.
00:00 Pizza Shop Example
01:40 Benefits of Asynchronous Processing
02:44 Scaling Shops (Horizontally)
03:10 Fault Tolerance
04:09 Features of a message queue
08:38 Encapsulation
09:38 Thank you!
Code: github.com/coding-parrot/Low-...
Looking to ace your next interview? Try this System Design video course! 🔥
interviewready.io
With video lectures, architecture diagrams, capacity planning, API contracts, and evaluation tests. It's a complete package.
Asynchronous Request-Response:
stackoverflow.com/questions/1...
www.enterpriseintegrationpatte...
Message Queue:
blog.codepath.com/2013/01/06/a...
highscalability.com/blog/2012/...
www.cloudamqp.com/blog/2014-1...
www.rabbitmq.com/getstarted.html
Load Balancing:
• What is CONSISTENT HAS...
You can find me here:
/ gkcs0
www.quora.com/profile/Gaurav-...
github.com/gkcs/
#message-queue #system-design #scalability #server
Notes to self:
* Servers are processing jobs in parallel.
* A server can crash. The jobs running on the crashed server still needs to get processed.
* A notifier constantly polls the status of each server and if a server crashes it takes ALL unfinished jobs (listed in some database) and distributes it to the rest of the servers. Because distribution uses a load balancer (with consistent hashing) duplicate processing will not occur as job_1 which might be processing on server_3 (alive) will land again on server_3, and so on.
* This "notifier with load balancing" is a "Message Queue".
Very good notes 👍
I don't understand why there might be a duplicate ?
the notifier will just query the tasks that handled by the cracked server and distribute them!
@@mahmoudelrabee2456 That is true if we store the server id also. This is explained as the first approach at @4:52
Consistent hashing and load balancer are 2 different things not same
The alternative approach is, instead of assigning individual task to server, you can let servers poll from the queue. In this case, your message queue is decoupled from application servers since message queue doesn't need to know anything about servers.
This guy reminds me of that friend that tries to explain and wrap up the whole semester for you 30 minutes right before the exam, because you didn't attend any lecture since the beginning.
great comment.... the way he is explaining its really wonderful
Lmao
dipak sonawane r
Exactly :)
those people are saints
Great job explaining everything in a way anyone can understand. You are a natural teacher! Please continue teaching and sharing your knowledge!
Thank you!
Former teacher turned Linux engineer here. Very well done explanation of this concept. Easy to follow with great usage of visuals and ongoing metaphor!
Explained the whole thing in literally the first 40 seconds. Truly amazing work!
Message queue is getting lots of spot light in the industry, please keep making the video on this topic i like you way of teaching. thanks again.
This was the best video so far. The way you explained the entire stuff without saying Message Queue the whole time awakened my grey cells. Thanks a lot!
I like the sheer excitement with which the topic is delivered!! Kudos!!
EXCELLENT job in all areas: Simplifying the use cases for explaining easily to non-experts, very VERY close examples to real-world instead of using hypothetical cases, starting from simple (in memory) to more complex approach (with database), and avoiding super technical jargon; yet not shying away from technical details (i.e. load balancing, hashing, etc.)
Well done Gaurav!! I enjoyed this video.
well said.
Hi Gaurav, This is the one of the best real life example (with pizza shop) showing the need of asynchronous request/response system. Thanks for the great video. Really loved it.
Thanks!
Thank you! Your tutorials are great! My college did not have System Design and Analysis class, and your videos helped to learn a lot.
Brother, I've been researching about message queues and I was so confused until I saw your video, thanks alot!
Again, thanks so much for taking the time to make this video. I've learned a lot from you. Keep it up!
😁
Are we just going to ignore the fact that 9 / 11 were pointing at the same server and THAT was the server that crashed! :P Your lectures are fun man!
Illuminati confirmed! Well done.
I am a java dev. For learning purpose I am planning to make queue system. But from your video i got idea that JMS is something I should learn now. Thanks Gaurav.
Your channel is amazing. Your explanations are some of the best I’ve ever heard/seen. Good job man.
know a days People like Bhaiya and didi on linkdln those who are giving lecture on system design other bla bla.. even don't know how to code, have more subscribers than this genuine talent. Hats of bro.😃
Amazing explanation Gaurav. The best way to explain any concept is with practical examples, and you did the same.
There are very less resource available for system design in youtube so please complete series . I like the way you teach. Thanks for making videos for us. God bless you
Thanks Sameer :)
"Very less", Very few. Indian English is hilarious though.
Bro, keep bringing up more videos like this. We are all such a big fan of yours. ALL the best! 👍
PS: Amazon has SQS ;)
great clear presentation!
one tip: use higher contrast ink and board.
So that means more lighting to make the board more lighter/white
and/or using dark ink like black or brown so we can see it more clearly.
great content. subscribed. keep up the good work!
The concept has been explained very clearly. It would be great if you would come with practical implementation using NodeJS with any MQ
Great Explanations of Sytem Design. Made fall in love with each concept.
The only youtuber that keeps his video at 9:59
Hahaha
HAHAHAHAHAHAHA
haha :?
back in the golden days of youtube everybody made videos to make videos, not to make money
Explained the concept really well , easy to understand
kya to samjaya hai Gaurav, maza aa gaya.. Such precise explanation is so rare on online tutorials.
You explained it so well, thank you
As a European developer that has seen too much low-quality programming disasters from projects outsourced to low-wage Asian country developers, I must say that it's refreshing to see an Indian engineer that has actually studied for this stuff and knows what he's talking about, using the correct terminology... I'm subscribing; you're creating great content.
Low-quality programmers are everywhere not just in Asia.
When to use a Topic vs a Que would have been a nice addition.
Gaurav, this is really a nice and knowledgeable tutorial you have made, in very sort time you have explained this topic very clearly. Can you try to make it as a practical ( how to implement RabbitMQ)
Thanks for the valuable video! It really helps me to understand what the message queue is :)
Nice explanation. You are actually doing excellent work. Thank you.
You are the best teacher. Thank you very much.
Appreciate your work!! thanks for sharing.
Very good job. I had so many confusion you just cleared
Thanks a lot for the content. Even I discussed the same heartbeat like mechanism (Got the idea from the video :P) in an interview. It was really helpful!
In a typical System design interview: Dabbe banao dabbe.. :D
so smart the way he is explaining. keep it up man
Damn man you are an amazing teacher. Subscribed!
Amazing work Gaurav, Keep inspiring!
Your charisma and you way of teaching gain me to be your subscriber :)
Excellent and lite tutorial on messaging and load balancing
Man, You are awesome.. the way you explain is truly great.😂
Gaurav, fantastic job with explaining the key tenants of high-level system design; how about bringing in some tooling and technology stack to support each of the architectures.
Very clear explanation. Thank you
Hey Gaurav, Thank you so much for the great explanation. Your videos are awesome. Keep up the great work.👍
Thanks!
Everyday you learn something new!
I always thought PS3 stood for PlaStation 3, but here I learn that it stands for PizzaShop 3.
"Now I know everything about how to run a restaurant; I will be starting my own restaurant very soon."
Thanks to the legend Gaurav.
Thats an excellent explanation Gaurav.. Thank you.
Nice narration..!! My pizza just got delivered under 30min
Great video! This video explains the system design of a pizza shop very well. However, it spends a lot of time explaining load balancers and the notifier and very few minutes are dedicated to discussing message queues. I am more interested in the actual use of message queues in real-world systems like pizza shop here.
"Filling up the coke can" 2:20 haha. Love your videos bro.
his expressions are hilarious !
Thanks for the great explanation man!!
Excellent explanation.
Thanks
Amazing explanation! Thanks!
You're welcome!
Great video. Would like a part 2
Maybe one on Apache Kafka and it's features :)
amazing series!
Excellent stuff - Cheers !!
Brilliant:-) good job. Really appreciable. Kindly make complete series on system design and soon start video series on python programming:-):-)
Gaurav! Its good conceptually. Thanks
Pretty well explained.
If you could cover on the concepts of real time operating systems- which includes tasks, task states, ,message queues and mailboxes etc..., It will be definetely helpful for me and for those who are interested in embedded computing and RTOS...
Super!!! Thank you Bro...
this is awesome explanation
Short.. To the point.. Brilliant 👍
Very giid analogies and articulation of topics..gr8 wrk.
Really nice explanation, impressive.
I've learnt a heck of a lot about how pizza shops work
Nicely and simply explained
@Gaurav Sen Very informative video! I request you to make a video or videos about every component of any system design. Different problems employ different components. If we first study all the different components and their properties then at least we can stay thinking in right direction. Thanks for your video series!
Hi Gaurav , can we have server id as one of the columns in the table and use that also while querying the DB , so that it picks only the undone orders by that server(dead server) only, and rest can be taken care by the load balancers which is distributing the load ?
We could, but wouldn't that complicate things? For example: A job is initially assigned to S0, then reassigned to S1 after S0 crashes. Now S1 crashes. The way to keep track of S1's jobs would be to update the server id on the DB. It's an extra update operation.
Now let's say a new requirement comes of evenly distributed load. In this case, when a new server comes up, it will take jobs from others. The db will again have to be updated.
Consistent Hashing seems like a cleaner solution :)
Nice explanation Gaurav, I was stuck on this only.
Yes, may be it requires querying DB more often to update the server ids. Its better to follow the principle of load balancing which implements the uniqueness.
Thanks. :)
But, if we are not maintaining system id along with each order, then whenever a server dies, we have to again see for all the orders, their nearest server. But, if we have server ids along with them then we would only have to assign the orders which are initially handled by the server that died.
If a new server is added, then we have to anyway check all the entries, then its fine but when a server dies wouldn't maintaining server id's would reduce our work. Anyways great video..!! thanks.
@@shiwanggupta8608 I agree, also let's say you are very large chain, and have thousands of orders in process at any given time, going though all of them seems a waste of time, when you can differentiate by just the server id.
great explantaion!
Really good video. Khub valo laglo dekhe.
Please create a video over HermesJMS. This video was really helpful in getting the basics of MQ
This is very clear and understandable. Subscribing..
Nicely explain
this is the first time I found the wrong explanation.
1. Once you have notified and it found that server 3 is dead then it can give that specific task to "assigner" node which basically divides the task and share between other nearest server to that location (it is important).
2. Each shop has to maintain his own task queue and "assigner node" would add those task in that queue based on priority ( but this will be least among its own task, as it requires to completes own task first then other. )
3. there is no use of centralized queue, until n unless you provide a feature to the pizza shop and based on user location pizza shop automatically (user did not select the shop which is always the case in dominoes at least) assign this task to the nearest shop.
4. Load balancer (if you were talking about the actual load balancer between servers) is no use for the assignment, as its responsibility to just equally divides the task across multiple servers within the same region for which this load balancer responsible for.
Dude, you should get a Ph.D. for this... made it easy to understand. Thanks for sharing.
This video ia really good, thank you
You don't necessarily need to assign a task to a specific server. A server that is ready can go and pull the pizza order from the queue and process it.
It is much faster
But what if a task was pulled , was in progress and then the server crashes , how do we make sure that this task, is again pulled by any up & running servers ?
@@kanishkamakhija9046 Notifier(which does the heartbeat check) could detect whether a server has crashed and mark the corresponding tasks to be unassigned.
Alternatively, a timeout could be added to each assigned task and if the in process task times out we remark it as unassigned and pick some alive server to handle it.
I also saw another approach where you can maintain a separate queue that holds in-progress tasks. If the server crashes, any other server can pick up tasks from the corresponding queue.
Cool!
Thanks for sharing.
We would like to have videos on object-oriented design patterns too like observer pattern etc.
Please keep making videos. :D
OOP is overrated and people are finally moving towards functional programming with NodeJS and React as some common examples
Good Teaching!!! Keep it up with great work
Thank you so much for good video
I like the way you explain it
This tutoria is GREAT
thanks for the informative presentation
Glad it was helpful!
Tech interviewer: Design dominoes pizza.
Me: :-)
Please confirm if my video understanding related to queues are correct :
When S3 crashed, we wanted to re-distribute the order no 9 and 11 to other pizza stores (s0 to s2).But server did not have record or order no's which were assigned to Pizza store S3.
Initially we thought of using 'Load Balancer' for this purpose.
(This is clear to me, so moving to queue now)
After that we improved our solution by using 'Message queues'. If we use 'Message queues' then we need to have one 'Queue' for each Pizza Store (Both at client and server side applications). Each pizza store will listen to its own 'Message queue'. Whenever a new Pizza is added to a 'Queue' (belonging to S3). when this Message is received by Pizza store S3 and acknowledged and then S3 starts processing it. If S3 is 'SUCCESSFULLY' able to complete it then message will be removed from the Queue at server side.
If S3 crashes then heart beats are not received and all messages stored in the Queue [belonging to Store S3] will be added to other store's Queues.
If S3 throws error/Exception (Enough Cheese not available for Pizza) during processing then message is still on server queue [Not a valid use case for current discussion]
Hi Gaurav, In the video where we discussed about duplicating order no. '3' between S3 and S2, the S2 is still up and running right? So will there be a case where load from S2 should be distributed to other servers? Will we be doing load balancing even if the Server is active?
Great explanation
banks, thats a fairly common use case that uses messaging services/queues extensively.
batch processing transactions, after the card scheme authorises your tx and the request is send to the issuing bank, the entire xml message is stacked up on a messaging queue that is being constantly listened to by the issuing bank messaging service
Well explained!
Nice explanation! Can you suggest resources to follow for system design?
Great Analogy!
for each system design if a detailed explaination is there, then, it will be helpful for all becoz i think i can learn system designs from you
thank you for your extraordinary work
Thanks David :)
Nicely done Gaurav!! Once again... :)
That 'filling up the coke can' face! LOL :D - thumbs up for a great video explanation!
Please make one video on Kafka. Appreciate your work.
Check learning journal challenge for Kafka video.