HTTP vs MQTT trade-offs in IOT Protocols - Performance Comparison

Time Complexity: HTTP vs MQTT trade-offs

O(n) for HTTP, O(1) for MQTT publish

Understanding Time Complexity

When comparing HTTP and MQTT protocols, it is important to understand how their communication patterns affect performance as the number of devices grows.

We want to see how the work each protocol does changes when more devices send or receive messages.

Scenario Under Consideration

Analyze the time complexity of message delivery in HTTP and MQTT.

// HTTP example: each device sends a request to server
for device in devices:
    send_http_request(device)
    wait_for_response()

// MQTT example: devices subscribe to topics
mqtt_broker = start_broker()
for device in devices:
    device.subscribe(topic)
publish(topic, message)

This code shows HTTP sending individual requests per device, while MQTT uses a broker to publish messages to many devices subscribed to a topic.

Identify Repeating Operations

Look at what repeats as devices increase.

• Primary operation: Sending messages to each device.
• How many times: HTTP sends one request per device; MQTT sends one publish to broker regardless of device count.

How Execution Grows With Input

As the number of devices grows, HTTP sends more individual requests, while MQTT sends one message that the broker distributes.

Input Size (n)	Approx. Operations
10	HTTP: 10 sends, MQTT: 1 publish
100	HTTP: 100 sends, MQTT: 1 publish
1000	HTTP: 1000 sends, MQTT: 1 publish

Pattern observation: HTTP work grows linearly with devices; MQTT work stays mostly the same for publishing.

Final Time Complexity

Time Complexity: O(n) for HTTP message sending, O(1) for MQTT message publishing

This means HTTP's work grows directly with the number of devices, while MQTT can send one message to many devices efficiently.

Common Mistake

[X] Wrong: "MQTT always uses less time because it sends fewer messages."

[OK] Correct: MQTT's broker handles distributing messages, which can add overhead as devices increase, so the total work is not always constant.

Interview Connect

Understanding how protocols scale helps you explain design choices clearly and shows you can think about system performance in real projects.

Self-Check

What if MQTT broker had to send individual messages to each device instead of one publish? How would the time complexity change?

Practice

1. Which protocol is best suited for devices that need to send data only when requested and have simple communication?

easy

A. FTP

B. MQTT

C. HTTP

D. CoAP

Solution

1. Step 1: Understand HTTP communication style

   HTTP works on a request-response model where the client asks and the server replies, making it simple and direct.

2. Step 2: Compare with MQTT style

   MQTT uses publish-subscribe, which is more complex and suited for many devices and continuous data flow.

3. Final Answer:

   HTTP -> Option C

4. Quick Check:

   Request-response = HTTP [OK]

Hint: Request-response means HTTP, publish-subscribe means MQTT [OK]

Common Mistakes:

• Confusing MQTT as request-response
• Thinking HTTP supports many-to-many easily
• Mixing up protocol purposes

2. Which of the following is the correct way to describe MQTT's communication pattern?

easy

A. Publish-subscribe

B. Request-response

C. Peer-to-peer

D. Broadcast

Solution

1. Step 1: Identify MQTT communication model

   MQTT uses a publish-subscribe model where devices publish messages to topics and others subscribe to those topics.

2. Step 2: Eliminate other options

   Request-response is HTTP, peer-to-peer and broadcast are different models not used by MQTT.

3. Final Answer:

   Publish-subscribe -> Option A

4. Quick Check:

   MQTT = Publish-subscribe [OK]

Hint: MQTT always uses publish-subscribe pattern [OK]

Common Mistakes:

• Choosing request-response for MQTT
• Confusing peer-to-peer with publish-subscribe
• Assuming MQTT uses broadcast

3. Consider a network with many IoT sensors sending small updates frequently. Which protocol will likely reduce network bandwidth usage?

medium

A. HTTP because it uses simple requests

B. MQTT because it uses large message headers

C. HTTP because it supports caching

D. MQTT because it uses lightweight messages and persistent connections

Solution

1. Step 1: Analyze network usage for many devices

   MQTT uses small message headers and keeps connections open, reducing overhead for frequent messages.

2. Step 2: Compare with HTTP overhead

   HTTP opens a new connection per request with larger headers, increasing bandwidth use.

3. Final Answer:

   MQTT because it uses lightweight messages and persistent connections -> Option D

4. Quick Check:

   Low bandwidth = MQTT lightweight messages [OK]

Hint: Persistent connections save bandwidth in MQTT [OK]

Common Mistakes:

• Assuming HTTP is lighter due to caching
• Thinking MQTT has large headers
• Ignoring connection overhead

4. You have an IoT device that must send data only when triggered by a server. You try using MQTT but the device keeps sending data continuously. What is the likely mistake?

medium

A. Using MQTT publish-subscribe instead of HTTP request-response

B. Not configuring the device to subscribe to the server's trigger topic

C. Using HTTP instead of MQTT

D. Setting QoS level to 0

Solution

1. Step 1: Understand MQTT trigger mechanism

   MQTT devices receive triggers by subscribing to topics; without subscription, they can't wait for triggers.

2. Step 2: Identify why device sends continuously

   If not subscribed, device may publish data on its own schedule instead of waiting for server commands.

3. Final Answer:

   Not configuring the device to subscribe to the server's trigger topic -> Option B

4. Quick Check:

   MQTT triggers need subscriptions [OK]

Hint: MQTT triggers require subscription to server topic [OK]

Common Mistakes:

• Confusing publish-subscribe with request-response
• Thinking QoS affects trigger behavior
• Switching protocols unnecessarily

5. You want to design a system where thousands of sensors send data to a central server, but the network is unreliable and bandwidth is limited. Which protocol and feature combination is best?

hard

A. MQTT with persistent sessions and QoS 1 or 2

B. HTTP with frequent polling

C. HTTP with caching enabled

D. MQTT with QoS 0 and no session persistence

Solution

1. Step 1: Consider network constraints

   Unreliable network and limited bandwidth require efficient, reliable message delivery without repeated data loss.

2. Step 2: Evaluate protocol features

   MQTT supports persistent sessions to resume after disconnects and QoS 1 or 2 to ensure message delivery.

3. Step 3: Compare options

   HTTP polling wastes bandwidth and lacks delivery guarantees; MQTT QoS 0 and no persistence risk data loss.

4. Final Answer:

   MQTT with persistent sessions and QoS 1 or 2 -> Option A

5. Quick Check:

   Reliable delivery + low bandwidth = MQTT QoS 1/2 + persistence [OK]

Hint: Use MQTT QoS 1/2 with persistence for unreliable networks [OK]

Common Mistakes:

• Choosing HTTP for unreliable networks
• Using MQTT QoS 0 when reliability needed
• Ignoring session persistence