I read a lot of posts and blogs at this stage, and I'm still not sure how to cluster my 2 RabbitMQ nodes correctly.
I read the RabbitMQ clustering guide: http://www.rabbitmq.com/clustering.html
I found out about the mysterious ClusterId in the API manual, without explaining how to get this identifier in the first place: http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v2.4.1/rabbitmq-dotnet-client-2.4 .1-api-guide.pdf
I learned in this StackOverflow article that I basically need my clients to know about each node in the cluster and the code for the script to switch to another resource: hp rabbitmq HA cluster
Now ... The behavior I would like to have is something more transparent, if possible. Where could I potentially use this "ClusterId" on the client to inform the consumer cluster, and I hope the library knows that it accidentally connects to node to capture messages.
Of course, I know that a message can only be on one server at a time, so I hope for some circular magic from the DotNet client library, which will also handle unsuccessful situations.
What I also hoped from the point of view of the publisher is that the exchange will cyclically distribute messages to various nodes of the cluster. The exchange will also have cluster knowledge and competently deal with errors.
, , ... .
, , , ... RabbitMQ ? ?
RabbitMQ ?