messaging - Ensure delivery of message, RabbitMq -


i know common approach create consumers queue before publishing message, seems pretty tight coupling going on here, don't want know how many queues consuming exchange , how messages each of them get, how can preserve reliability while decoupling server consumer?

enter image description here

on image client-app still needs know if there server queues available process auth request. because if there no queues message dead lettered, don't believe no 1 ever though this? or presume queues exists (they durable)?

the way rabbitmq , amqp 0.9.1 in general works not couple sender of message consumer. can query exchange using many different methods find out queues bound it, @ time send message never sure available unless create queue , binding yourself.

1 way can check sure message not placed onto queue use publisher confirms. possible asynchronous way listen notification on standard rabbitmq logging exchange message dlq'd.


Comments

Popular posts from this blog

user interface - how to replace an ongoing process of image capture from another process call over the same ImageLabel in python's GUI TKinter -

javascript - Restarting Supervisor and effect on FlaskSocketIO -

php - Mongodb connectivity error -