Optrix:
My user-base is largely going to want to connect their LoRaWAN data to cloud IoT infrastructure - namely AWS IoT Core, Pub/Sub and Azure IoT - rather than use the local MQTT broker. But I was hoping to use a single server on our end to handle this.
My hope was that the product would let me quickly and easily bridge an orgs data to a destination - and the HTTP endpoint does allow this, but it requires someone to get in there and fiddle with the plumbing.
Slightly offtopic as this is not related to MQTT, but this will be included in the next ChirpStack Application Server (test) release:
This should make it a lot easier to integration with cloud providers (AWS, Azure and GCP). These integrations will all be using HTTP(S) calls so the connection-pool/-cache does not apply.
3 Likes
