A simple IoT architecture to Ingestion and Reporting — Part II
Part I | Part III | Part IV | Part V| Part VI
Context
In the last article, we covered some general aspects of the IoT architecture, in this second part, of a series of articles, we will start to cover some technical aspects of the architecture, like services, which kind of brokers, databases, and frameworks to use.
In this part, we will cover the MQTT broker and the Edge Service.
Disclaimer
I chose the Spring Framework to create the architecture because my main program language is Java and I have a big experience with Spring. It’s only a preference, you can recreate all of this architecture using another program language.
Big Picture
If we could compare the MQTT broker and Edge Service to a part of the human body, we probably choose the heart, because all the information of the system is provided from this point and “pumped” to all points of the system.
MQTT Protocol + Broker
The MQTT broker has the main responsibility of receiving the incoming information from the IoT devices, the Broker uses the MQTT protocol, which represents a protocol simple and lightweight.
