I have searched for similar questions, but they are related to older versions of ChirpStack.
In order to scaling and making ChirpStack HA, we must make HA all its components.
Regarding the main fundamental components:
chirpstack: it is not clear if this component can be replicated safely, since it interacts with postgeres, redis, etc.
chirpstack-gateway-bridge: this seems to interact with the MQTT broker and the gateways, so maybe it can be scaled by putting it behind a load balancer w.r.t. the gateways. Not sure regarding the the broker
chirpstack-rest-api: not clear if it is completely stateless
- other components: out of scope! It is not a ChirpStack issue to make the broker or the DB HA
So, can someone clarify if there is a reliable way to deploy ChirpStack in HA?
thank you for the reply.
Unfortunately I do not see any simple way to ensure the routing for the UDP data of
chirpstack-gateway-bridge to always go to the same instance. So this is the only weak point. Maybe this could be a feature for the future releases.
The other components are stateless or with the state stored on external DB’s, so they can be easily scaled: good news
I recommend running Gateway Bridge (or MQTT Forwarder) on the gateway instead of sending plaintext UDP over the Internet. Two birds, one stone.
“I recommend running Gateway Bridge (or MQTT Forwarder) on the gateway”
Can you recommend some sub-$1000 gateways that allow this (make & model)?
The MQTT Forwarder and Gateway Bridge Installation pages list all the supported gateways for on-gateway installation:
I’m a fan of the MultiTech Conduit AP, which is much less than your given price limit, but the low-cost Dragino models also look pretty promising. I know the LPS8N works with the MQTT Forwarder.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.