New DevHeads get a 320-point leaderboard boost when joining the DevHeads IoT Integration Community. In addition to learning and advising, active community leaders are rewarded with community recognition and free tech stuff. Start your Legendary Collaboration now!
I am currently working on a personal project where I have serveral iot devices which have several sensors attached. However, I am not quite sure about the best way to design the communication flow. Specifically, I need both real-time data and historical data.
Initially, I thought about having an MQTT broker for communication between my iot devices and backend (django) and then through my backend I can use websockets to forward real-time updates to my mobile app and http for historical data. However, I’m unsure if this is the most efficient approach or if I should consider having the mobile app directly communicate with the MQTT broker for real-time data.
As per my understanding this approach will be best. it will be a bit complicated if mobile app will directly communicate with mqtt broker. let`s what other people suggests.
I participated in several initiatives where mobile apps used MQTT to communicate with devices and/or backend systems. MQTT does not increase the complexity compared to web socket communication, but not every developer knows this protocol and can properly design the MQTT Topic structure.
CONTRIBUTE TO THIS THREAD