What is Message Queueing? Message Queue explained.

[@dahliaferrer2098]

EXCELLENT, explanation. I now feel like I understand asynchronous message queues and I'm not a developer. TY for the graphics, the thoughtful presentation. Very appreciated!

[@lester_cch9877]

I LOVE YOU! GOD BLESS YOU! Always trying to understand this and now it's been very simple with the queue message example with Dinner system.

[@PancitoTostado]

Great job modeling the queue and their examples :)

[@bayesian7404]

great job. I look forward to watching more videos from you on MQ.

[@rainingjokerRevived]

nice and fast way of explaining the concept and how it's useful

[@CloudAMQP]

Thank you!

[@LittleTechExplorer]

very well explained with a beautiful presentation 👍

[@ksgdeveloper]

Very well explained. Please add more videos. thanks

[@baracjohn3913]

really nice explanation

[@kevinnguyen9703]

Very nice, simple visual of async vs sync

[@027KANDUKURIBALAVIKASH]

What if MQ is full? or it went down for a period of time? Maintaining a Redundant MQ is costly and not effective solution i guess. Any other alternative?

[@RuslanSkiraUkraine]

Thank you for your work. Maybe you work with celery? ) I'm interested in how to work in the situation with 'dead letter queue' in Celery.

[@darthvader_]

I have a question. What happens if the consumer consumes the message and for some reason crashes. How do you make sure that the message in the queue (before the consumer failed) is serviced? Do you maintain another queue? or something like a log that captures the state? pass on to a different consumer (assuming ur system is scaled)?

[@CloudAMQP]

You can use acknowledgements in RabbitMQ, where the consumer needs to ack the message before it is removed from the queue.

[@irfanafzalkhan5786]

Great job

[@GidzPaul]

Thank you

[@m_t_t_]

When does the queue service remove the data from the queue and send it to the microservice? eg, how does the queue service know that there are items waiting in the queue?

[@CloudAMQP]

Let's take the protocol AMQP 0-9-1 as an example (used by RabbitMQ). Here we use an acknowledgement/confirm mechanism that the message has been received by the consumer, and/or the task has been completed. Automatic acknowledgements are usually called "fire-and-forget" and tells the queue to discard the message when it's sent successfully. Manual acknowledgements on the other hand requires some logic to be implemented on the consumer side (microservice), that sends a command back to the queue once it's been successfully processed (ack) or failed to complete (nack). The latter allows the queue to re-add the message into the queue if it never receives an ack from the consumer, or if it receives a nack. Which method to use all comes down to your specific use case for the specific queue, and the importance of the data that is sent. Every microservice establishes a connection + channel to the queue that is long lived. So a message is delivered automatically to any microservice that is connected to the queue and ready to receive messages. If there are no consumer available, the message is stored safely in the queue until it can be delivered.

[@m_t_t_]

@@CloudAMQP Thank you very much. I understand now

[@myadarapuakhil9560]

Thanks!

[@martinabeita8852]

aren't message queue and message broker different?

[@namenone8387]

no comments?

[@michaelprice8402]

Does this get used on KZbin Live Stream Chat? I have a background running system having a problem with MFResident.exe Is this affiliated with Message Queuing Service?