RabbitMQ- Tutorial 10a - Pub/Sub Python Implementation

[@monakanafi1057]

Great explanations. Very easy to follow, and with a perfect flow of information. Thanks for your contribution!

[@jumpstartCS]

Thanks for the support Mona! Glad you enjoyed the content!

[@sandromeireles7715]

Great video, it helped me a lot, thanks.

[@jumpstartCS]

Glad to hear it helped! Thanks for your support :-)

[@akshaynitin5589]

In exchange_type = "fanout" is correct

[@MehrdadMahmoodpoor]

👌👌👌👌❤❤❤❤❤❤

[@tongtony3880]

if first consumer and second consumer are no connect to queue. The message will keep in the queue?

[@jumpstartCS]

Yes the message will remain on the broker until a consumer acknowledges it's consumption. Obviously this behavior can vary depending on your specific setup but this is the default I believe

[@anandmahurkar4157]

Hi, Instead using localhost, Can I use IP address?

[@jumpstartCS]

While not covered in this video you can host rabbitmq however you want. For an easy option check out cloud ampq.

[@RadosławHryniewicki]

But does the exchange declaring in consumers is necessary? I guess only the exchange name (in our example - 'pubsub') is crucial to receive messages from consumer unique queue, doesn't it? What is funny, I commented the line with declaring exchange in consumers and the application works as it should (when msg is broadcasted from producent, all consumers received this message)

[@jumpstartCS]

It's been awhile since I've worked with this but I believe the answer is yes, an exchange declaration is required for a consumer to subscribe. What is possible in this case is that the exchange was previously declared by a producer or another consumer (even another instance of the same consumer). That way it works. Maybe try either removing the exchange from the web interface and run the consumer again, or just run the consumer but enter a brand new exchange name.