I am building a cluster setup and plan to use a network loadbalancer that routes UPD and TCP to container stacks. Each container stack contains
- Gateway Bridge
- Network Server
- Application Server
- MQTT Broker
The stateful components Redis and Database have their own cluster so each container stack communicates with the same stateful components. Now I am wondering if I have to pull out the MQTT Broker out of the stack as well. The documentation states:
For performance and to make the ChirpStack Gateway Bridge highly available, you can run ChirpStack Gateway Bridge on multiple servers, each connecting to the same MQTT broker.
Is there any drawback in having each container stack having its own MQTT broker? The only issue I can think of is that I might not see frames in the UI from a different container. But that would not be as problematic in my case. Any thoughts are welcome.