![]() To support the MQTT protocol, as mentioned above, the Gateway requires a broker MQTT, accessible via the network, preferentially located on the same host of the Gateway.The Gateway is distributed in a single, self-consistent JAR file. ![]() Regarding the dependencies on external components and modules: For example: deploy the Gateway, Visualization Server and Broker in three Docker containers, orchestrated via Kubernetes (K8S), or Docker Compose. ![]() Obviously, alternative distributions could be considered. Support for the MQTT protocol requires an MQTT broker (shown in blue), which is assumed to be distributed in the same VM of the Gateway.The Visualization Server, based on an OpenSource ( Traccar), runs in a second OCI VM.The Cloud Gateway runs inside a first virtual machine (VM), distributed in Oracle Cloud Infrastructure (Oracle Generation 2 Cloud, OCI).The overall architecture of the solution is shown in the following picture. Then, at a later time, I have extended the Gateway to support the MQTT protocol as well.Īll the code is made available in the GIT repository. The implementation presented here was born for a Proof of Concept (PoC) for a specific customer, in which case the protocol used by the vehicles is HTTP and the application message consists of a string of characters, with a defined format. ![]() Today, in IoT field, the MQTT protocol is more and more adopted, due to its superior efficiency and reliability. Many solutions born in the pre-IoT world, when for example the acronym M2M was used, are based on the HTTP/S protocol for the communication between device and server-side solution.
0 Comments
Leave a Reply. |