Understanding IoT Data Protocol - PyCon ID 2018
0 likes91 views
This document summarizes common data protocols used for IoT devices. It discusses HTTP for one-way client-server communication, WebSocket for persistent full-duplex connections in a browser, and MQTT for lightweight publish-subscribe messaging between IoT devices and brokers. MQTT is highlighted as particularly suitable for IoT due to its small code footprint and ability to handle limited bandwidth connections. Performance tests show MQTT significantly outperforms HTTP for consistent transmission of time-sensitive data. The document encourages choosing the right protocol based on use case and mentions some popular message brokers.
Understanding IoT Data Protocol - PyCon ID 2018
- 1. Understanding IoT Data Protocol Tegar Imansyah - 4 November 2018
- 2. About ● Backend Engineer for Ngabarin IoT Platform ● Surabaya.py Organizer ● Mechatronics Engineering from PENS ● Interested in: Microcontroller, Raspberry Pi, Linux, Web, Data Get in touch: http://github.com/tegarimansyah http://t.me/tegarimansyah http://linked.in/tegarimansyah
- 3. Agenda ● Understanding IoT ● HTTP Request ● WebSocket ● MQTT ● Conclusion
- 4. Are you familiar with... Web framework Microcontroller WebSocket Communication Protocol
- 5. What is IoT IoT = Internet of Things, a fancy buzzword when we talk about Industry 4.0 The Internet of things is the network of physical devices. Combination from electronics, software, sensors, actuators, and connectivity which enables these things to connect, collect and exchange data. - Wikipedia, with adjustments.
- 6. Electronics Software Sensors Actuators Connectivity Light Sensor Humidity Sensor Water Pump Microcontroller Server
- 8. Why IoT Device Different With Computer Google Cloud F1-micro (Smallest) ● 0.2 vCPU Intel Xeon E5 ● Memory: 0.6 GB = 588 MiB ESP32 (Popular Powerful Microcontroller) ● CPU : Dual Core 240 Mhz ● Memory: 520 KiB Arduino Uno (ATmega328) - (Most Popular dev board) ● CPU : 20 Mhz ● Memory: 2048 B = 2 KiB
- 9. What to discuss ● HTTP ● Websocket ● MQTT
- 10. HTTP HTTP is a request–response protocol in the client–server computing model. Request is usually using REST - GET, POST, PUT, DELETE Response with status code: 200 - OK 201 - Created 400 - Bad Request etc….
- 11. Test HTTP Server Side Client Side
- 12. Light Sensor Humidity Sensor Water Pump Microcontroller Server Problem: How to send data to Microcontroller in Real Time?
- 13. WebSocket Websockets allows persistent connections with simultaneous bi-directional communication. They come with all the benefits of HTTP since websockets initially start off as an HTTP handshake, before getting elevated to continue the rest of the communication in websockets.
- 15. MQTT MQTT is a publish-subscribe-based messaging protocol. It works on top of the TCP/IP protocol. It is designed for connections with remote locations where a "small code footprint" is required or the network bandwidth is limited. The publish-subscribe messaging pattern requires a message broker.
- 16. MQTT 16 Brokertable-lamp room-lamp subscribe table-lamp subscribe room-lamp subscribe table-lamp subscribe room-lamp subscribe table-lamp subscribe room-lamp
- 17. MQTT 17 Brokertable-lamp room-lamp publish table-lamp (255,0,0) receive table-lamp (255,0,0) receive table-lamp (255,0,0)
- 18. Who is Broker? Adafruit.io Google Cloud IoT Core
- 20. What to learn about MQTT ● Topic ○ Wildcart = home/+/lamp ○ Wildcart = home/bedroom/# ● User & Access Control List (ACL) ○ %u/home/bedroom => for user == tegar, only able to access tegar/home/bedroom ● Quality of Service (QoS) ○ 0 ○ 1 ○ 2 ● Broker Bridging
- 21. MQTT over WebSocket (?) => HTTP, HTTPS, FTP, FILE MQTT <> HTTP, HTTPS WebSocket == HTTP (HTTPS via wss)
- 22. MQTT over WebSocket TCP/IP Physical Layer : HTTP WebSocket MQTT Browser
- 23. HTTP vs MQTT performance tests Credit to: https://flespi.com/blog/http-vs-mqtt-performance-tests 1K Messages Bytes Transmitted Mosquitto MQTT Client MQTT over SSL 1 Publish per msg 283.743 5.911 HTTPS 1 POST per msg 15.373.263 115.669 HTTPS 1 POST with 1000 msg 20.515 0.307 Conclusion: MQTTS is 20 times faster and requires 50 times less traffic on the task of posting consistent time-valuable data.
- 24. Conclusion ● Be wise to choose your protocol, there is no One Size Fits All ● HTTP best for one way transmission (client-to-server) Websocket best for full-duplex persistent connection in browser MQTT best for persistent connection in IoT ● Many other message broker you can try: AMQP, Kafka, etc. They best on their own purpose.
- 25. Ready to Play with IoT? ● No Undo ● Unseen ● Broken = Start from Beginning ● Very Fun!
- 26. Thanks! Any questions? You can find me at @tegarimansyah Get slide and code: https://github.com/tegarimansyah/presentation/tree/PyCon-ID-2018