# access workers, routers, transports objects from one node process to another **URL:** \ **Category:** mediasoup libraries\ **Created:** [July 25, 2022, 5:54am UTC](https://mediasoup.discourse.group/t/access-workers-routers-transports-objects-from-one-node-process-to-another/4403 "2022-07-25T05:54:10Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\ **Post date:** [July 25, 2022, 12:13pm UTC](https://mediasoup.discourse.group/t/access-workers-routers-transports-objects-from-one-node-process-to-another/4403/6 "2022-07-25T12:13:51Z")
The broker server acts as a mediator for all the servers, you’d connect all media servers to this broker as well chat servers. You’d keep track of servers, rooms, broadcasts, subscriptions and more through this server. A bit tough to explain but see it as if we had one room on two servers we’d need a mediator, we’d need to send the message to a server to fan it out. So in this setup, broker calls every shot and may perform tasks like, CloseBroadcaster, CloseConsumers all sorts and will need to know which server consumed/produced/etc. * * * As far as I’ve seen, there’s no solution ready-made for this type of stuff, so it’s all going to be custom generally for your app. --- _[View the full topic](https://mediasoup.discourse.group/t/access-workers-routers-transports-objects-from-one-node-process-to-another/4403)._