RabbitMQ Getting Started

[@saurabhchauhan232]

Very nicely explained including installation. Thank you. Don't know how this came to my mind but a debugging or profiling series (tips and tricks) would be really helpful. If this is possible 😀

[@Matlus]

Thank you Saurabh and yes I've been meaning to do a couple of videos on Keyboard shortcuts, and debugging and debugging keyboard shortcuts etc.

[@yanzhainie484]

Very helpful, Thanks very much. Hopefully you can make some videos about kafka and mongoDB.

[@ibrahims9278]

Great presentation. Weldone.

[@Matlus]

Thank you Ibrahim!

[@VladyslavPavliuk]

Thanks for the video!

[@Matlus]

You're most welcome Vlad! Glad you're enjoying my videos.

[@vikneshrajsp]

Nice explanation. Regarding the competing consumers with manual ack and prefetch count = 1, let us say consumer-1 takes more time, will the same message be delivered to consumer-2 as consumer-1 is not acked yet?

[@Matlus]

In the message broker there is a timeout before which an ack should be received (www.rabbitmq.com/consumers.html#acknowledgement-timeout), if an ack is not received within that period, the message will reappear in the queue.

[@vikneshrajsp]

@@Matlus Thank you!

[@VinuP2023]

Shiv, congratulations for 5k subscribers mark :)

[@Matlus]

Omg! Thank you Vinay!

[@RalfHönscher]

Hallo, and thank you for this presentation. First sorry for bad english and second I am new in C#. I have a question. For me the listener is a new thread. And channel is from the UI-Thread. Why it its possible to use channel in the listener. What I have done, is EventingBasicConsumer basicConsumer = (EventingBasicConsumer)sender; IModel _channel = basicConsumer.Model; Is this wrong?

[@mnaveen24]

Sir, would you recommend using the method of creating a task from TPL as a subscriber to rabbitmq instead of creating many processes as a subscriber

[@loyolastalin]

Hi Shiv, Can you give more insight on Chanel + Mutex/ Semaphore that you have explained here or please provide me some reference pointer?

[@Matlus]

Hi Loyola, I don't recall in what context. Can you point me to a time in the video please. Mutex and Semaphore are thread synchronization primitives (At the operating system level). Mutex (Mutually Exclusive) . In short a Semaphore is for signaling from one task to another, while a Mutex is taken and released, always in that order, by each task that uses the shared resource it protects. Without any context it is difficult to understand or explain :).

[@pramuk9998]

Suggestion: explanation and presentation is very good. But I think if you show code more and your face in side panels then it will be more meaningful.

[@Matlus]

Code is available on my GitHub if you need to see it in more detail. Link is in the description

[@orhn]

@@Matlus It is hard to follow when you change code to full screen face cam. You can put the mini face cam on top of full screen code display.

[@Matlus]

@@orhn Code is available on github.

[@HIOLLJ]

Good work Shiv, Kudos :)

[@Matlus]

Thank you Gourav! Glad you liked it. Stay tuned for the next on Azure ServiceBus

[@santanukar5069]

Great video. Can you go a bit more in-depth to rabbitMQ and how to scale it?

[@Matlus]

The best source of that information will be the RabbitMQ website

[@sendersender8050]

very very confusing video (it would have been better not to try to explain so much and just do it)

[@Matlus]

Sorry to hear.