Publish-subscribe architecture in IOT Protocols - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main idea behind the publish-subscribe architecture?

It is a messaging pattern where senders (publishers) send messages without knowing who will receive them, and receivers (subscribers) get messages they are interested in without knowing who sent them.

beginner

In publish-subscribe, what role does the broker play?

The broker acts like a post office. It receives messages from publishers and delivers them to subscribers based on their interests (topics).

beginner

What is a 'topic' in publish-subscribe systems?

A topic is a label or category that messages are tagged with. Subscribers listen to topics they care about to receive relevant messages.

intermediate

How does publish-subscribe architecture help in IoT devices communication?

It allows devices to send and receive data efficiently without direct connections. Devices publish data to topics, and others subscribe to those topics to get updates.

intermediate

Name one advantage of using publish-subscribe over direct messaging.

Publish-subscribe decouples senders and receivers, making the system more flexible and scalable because they don't need to know about each other.

What component in publish-subscribe architecture manages message delivery?

A Broker

B Publisher

C Subscriber

D Client

The broker receives messages from publishers and sends them to subscribers.

In publish-subscribe, who decides which messages to receive?

A Subscriber

B Broker

C Publisher

D Network

Subscribers choose topics they want to receive messages from.

What is a key benefit of publish-subscribe architecture?

A Direct connection between devices

B Decoupling of senders and receivers

C Faster hardware

D Manual message routing

Publish-subscribe allows senders and receivers to operate independently.

Which of these is NOT a part of publish-subscribe architecture?

A Broker

B Subscriber

C Database

D Publisher

Database is not a core component of publish-subscribe messaging.

What does a subscriber use to filter messages?

A IP address

B Protocol

C Port number

D Topic

Subscribers listen to specific topics to get relevant messages.

Explain how the publish-subscribe architecture works in simple terms.

Think of it like a newspaper system with writers, a post office, and readers.

Describe the benefits of using publish-subscribe architecture in IoT systems.

Consider how many devices can communicate without knowing each other directly.

Practice

1. What is the main role of a broker in a publish-subscribe architecture?

easy

A. To receive messages from publishers and forward them to subscribers

B. To directly connect publishers and subscribers

C. To store all messages permanently

D. To encrypt messages between devices

Solution

1. Step 1: Understand the broker's function

   The broker acts as a middleman that receives messages from publishers.

2. Step 2: Identify message forwarding role

   The broker forwards these messages to subscribers interested in specific topics.

3. Final Answer:

   To receive messages from publishers and forward them to subscribers -> Option A

4. Quick Check:

   Broker forwards messages [OK]

Hint: Broker forwards messages, it doesn't connect devices directly [OK]

Common Mistakes:

• Thinking broker connects devices directly
• Assuming broker stores messages permanently
• Confusing broker with encryption service

2. Which of the following is the correct way to describe a topic in publish-subscribe?

easy

A. A label used to organize messages for subscribers

B. A direct connection between two devices

C. A security protocol for message encryption

D. A device that publishes messages

Solution

1. Step 1: Define what a topic is

   A topic is a label or category that organizes messages so subscribers receive only relevant ones.

2. Step 2: Eliminate incorrect options

   Topics are not connections, security protocols, or devices.

3. Final Answer:

   A label used to organize messages for subscribers -> Option A

4. Quick Check:

   Topic organizes messages [OK]

Hint: Topics organize messages, not devices or connections [OK]

Common Mistakes:

• Confusing topics with device connections
• Thinking topics are security features
• Mixing up topics with publishers

3. Given this scenario: A device publishes messages to topic home/temperature. Which device will receive the messages?

medium

A. All devices on the network

B. Any device subscribed to home/humidity

C. Any device subscribed to home/temperature

D. Only the publishing device

Solution

1. Step 1: Identify the topic published to

   The device publishes to home/temperature.

2. Step 2: Determine which subscribers get the message

   Only devices subscribed to home/temperature receive the messages.

3. Final Answer:

   Any device subscribed to home/temperature -> Option C

4. Quick Check:

   Subscribers to topic get messages [OK]

Hint: Subscribers to the exact topic get messages [OK]

Common Mistakes:

• Assuming all devices get messages
• Thinking publishing device receives its own messages
• Confusing similar topic names

4. A subscriber is not receiving messages from the broker. Which of these is a likely cause?

medium

A. Publisher is sending messages to the subscriber directly

B. Subscriber is publishing messages instead of subscribing

C. Broker is encrypting messages incorrectly

D. Subscriber is not subscribed to the correct topic

Solution

1. Step 1: Check subscription correctness

   If the subscriber is not subscribed to the right topic, it won't get messages.

2. Step 2: Rule out other causes

   Publishers don't send messages directly; encryption issues or wrong roles are less common causes here.

3. Final Answer:

   Subscriber is not subscribed to the correct topic -> Option D

4. Quick Check:

   Correct topic subscription needed [OK]

Hint: Check subscriber's topic subscription first [OK]

Common Mistakes:

• Thinking publisher sends messages directly
• Blaming encryption without evidence
• Confusing subscriber and publisher roles

5. In a large IoT system using publish-subscribe, how can you ensure that only devices in the 'factory/floor1' area receive temperature alerts without affecting others?

hard

A. Publish all alerts to factory/temperature and let devices filter messages locally

B. Publish temperature alerts to topic factory/floor1/temperature and have devices subscribe to it

C. Send alerts directly to each device's IP address

D. Use a single topic temperature for all devices

Solution

1. Step 1: Use topic hierarchy for targeted messaging

   Publishing to factory/floor1/temperature targets only devices subscribed to that specific area.

2. Step 2: Avoid broad topics or direct device addressing

   Broad topics or direct IP messaging reduce scalability and flexibility.

3. Final Answer:

   Publish temperature alerts to topic factory/floor1/temperature and have devices subscribe to it -> Option B

4. Quick Check:

   Use specific topics for targeted delivery [OK]

Hint: Use detailed topic paths for precise message delivery [OK]

Common Mistakes:

• Using broad topics causing unwanted message delivery
• Trying direct device IP messaging in pub-sub
• Ignoring topic hierarchy benefits