5
MQTT Vs. HTTP for IoT
source link: https://www.infoq.com/vendorcontent/show.action?vcr=883e5d99-1299-493e-ba55-98c42e3eb362&itm_source=infoq&itm_medium=VCR&itm_campaign=vcr_homePage_click&itm_content=bottom&vcrPlace=RVC&pageType=HOMEPAGE
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
InfoQ Homepage MQTT Vs. HTTP for IoT
MQTT Vs. HTTP for IoT
Company: HiveMQ
MQTT was designed for the Internet of Things (although it wasn’t called that at the time) whereas HTTP was created to make documents available across the internet. They both run over TCP connections, and are both client-server in architecture, but MQTT allows messages to pass in both directions between clients and servers whereas HTTP servers only respond to requests from clients.
Learn more about:
- The fundamental differences between the MQTT and HTTP protocols
- Measuring and comparing performance between the two protocols
- The advantages and disadvantages of MQTT in IoT
- The advantages and disadvantages of HTTP in IoT
- Which is ultimately better for IoT
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK