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?