> For the complete documentation index, see [llms.txt](https://docs.antares.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antares.id/en/code-and-library-examples/esp32-wi-fi/http-and-mqtt-protocol.md).

# HTTP & MQTT Protocol

In sending data to the internet-based Antares platform, two protocols are provided that can be tried, namely MQTT and HTTP.

### MQTT

The MQTT (Message Queuing Telemetry Transport) protocol is a communication protocol designed for lightweight message exchange between devices connected to a network. MQTT is particularly popular in Internet of Things (IoT) applications, where devices such as sensors, microcontrollers, or other smart devices need to communicate with each other.

### HTTP

The HTTP (Hypertext Transfer Protocol) protocol is also used in the Internet of Things (IoT) for communication between IoT devices and connected servers or services. The HTTP protocol in the context of IoT plays a role in data exchange between IoT devices and the infrastructure that supports them.

### Comparison of MQTT and HTTP Protocols

| **Parameter**       | **MQTT**                                                | **HTTP**                                              |
| ------------------- | ------------------------------------------------------- | ----------------------------------------------------- |
| Power Usage         | Lightweight in resource utilisation                     | Heavier on resource utilisation                       |
| Communication Model | Publish-subscribe                                       | Request-response                                      |
| Overheard Protocol  | Low                                                     | High                                                  |
| Scalability         | Large enough to handle multiple devices and connections | Has a limited number of devices and connections       |
| Connection Control  | Managed by an MQTT server (broker)                      | Connections must be made and maintained by the client |
| Efficiency          | Suitable for IoT protocols                              | Suitable for web applications                         |