Lets say I have multiple websocket servers that maintain many connections to clients to send updates. These websocket servers will be pulling said updates from a rabbitmq broker, and broadcasting them to all relevant clients who happen to be on a page that needs an update.My question is how can all clients who are on page[x] get an update for it if they are split up across multiple websocket servers? WS-server-A will recieve an update and forward it out to all its clients on page[x], but whate about the clients connected to WS-server-b who has clients on the same page?(edited below to add more details)The way I'm imagining this scenario is like so:For an imaginary forum, we have a multi-threaded web server that does page rendering and responds to api calls. When someone saves a post on a topic, the web server saves the post to the db, then passes the post off to rabbitmq.Rabbitmq forwards this post to the relevant exchange (say, 'new-posts'. There are also other exchanges: 'new-topics', 'alerts', etc), where the websocket server picks it up, examines the header and forwards the post to all users who are on the relevant page.
How can an update message from a rabbitmq broker reach all relevant clients via multiple websocket servers?
web services;message queue;websockets;messaging;message passing
What probably happens right now is that some messages are processed by server A, and never delivered to B, and some are processed by B, but A never receives them. This is because you haven't specified the exchange: the default one is the direct exchange, meaning that messages are sent to one of the queues at a time, using round robin.In order for multiple servers to receive the message, you may use the fanout exchange routing. With this type of routing, the same message will be routed to every queue.The exchange routing type is specified when you create the exchange.You can find additional information about different types of exchanges on the official RabbitMQ website.