MQTT glossary
Message routes, client roles and delivery state in the boiler house.
Access-control list
Rules setting which topics a client identity may read or write.
An ACL sets the topic permissions for a client identity at the broker. A filter expresses interest, while permission determines whether that interest is allowed.
Boiler example: The screen needs permission as well as a matching temperature filter.
Also see: Authorization, Authentication, Topic filter
Authentication
A check of a client’s identity.
Authentication asks whether the expected identity connected. It is separate from checking what that identity is allowed to publish or receive.
Boiler example: Check whether the expected boiler sensor connected.
Also see: Authorization, Access-control list, Broker
Authorization
A check of what a client identity is permitted to do.
Authorization asks whether an identity may publish to or read a topic. Keep evidence of both permitted and denied routes at the broker.
Boiler example: Check whether the boiler sensor may publish to its topic.
Also see: Authentication, Access-control list, Topic
backoff
Backoff makes the wait between failed attempts grow.
The recovery policy must say how waits change, where the retry count is kept and what happens when attempts run out. The receiver still needs to show that useful work resumed.
Boiler example: Bex increases the boiler sensor’s wait after failed reconnect attempts and checks the dashboard for a fresh reading after recovery.
Also see: exponential backoff, retry budget, jitter
Backoff with jitter
Backoff with jitter means increasing the wait between retries and adding a random change to spread clients’ attempts over time.
Without that spread, clients can return in synchronized waves. Spreading reconnects helps avoid presenting all the recovery work at once.
Boiler example: Bex spreads the house devices’ reconnect attempts while they wait to send readings or receive commands again.
Also see: backoff, jitter, retry budget
Broker
A service between publishers and subscribers that routes permitted messages using topic matches.
The broker compares a publication’s topic with subscription filters and forwards permitted matches. Broker acceptance alone does not prove that a subscriber received the message.
Boiler example: Bex’s broker forwards the boiler temperature to matching listeners.
Also see: Publisher, Subscriber, Topic filter
callback
A callback is a function registered to handle an event, such as an incoming message.
Assign handlers before connecting and starting network service so early messages have a handler available. A registered handler alone does not establish a successful connection or a received reading.
Boiler example: Bex checks the dashboard’s message callback for the boiler reading rather than relying only on a connection message.
Also see: network loop, subscription, observability
certificate
A certificate is a security credential used to validate the identity of a connection endpoint.
The client must check the broker’s certificate and hostname. Accepting an invalid certificate defeats that identity check even when the traffic is encrypted.
Boiler example: Bex tests that the boiler sensor rejects a broker presenting an invalid certificate.
Also see: TLS, mutual TLS, Authentication
clean session
A clean session starts fresh and discards session state when the client disconnects.
It can suit a sensor that only publishes replaceable readings and has no incoming commands to remember. Readings the sensor cannot send need storage on the sensor itself.
Boiler example: Bex considers a clean session for the boiler sensor when its next routine reading can replace a lost one.
Also see: session state, persistent session, local buffer
Clean Start
Clean Start is the MQTT 5 setting that chooses whether a connection starts a new session.
Starting fresh and keeping state after disconnection are separate choices in MQTT 5. Requesting an old session cannot recover a record that has already expired.
Boiler example: Bex checks the valve’s Clean Start request against the broker’s report of whether its saved session survived.
Also see: Session Expiry Interval, Session Present, client ID
client ID
A client ID is the identifier the broker uses to find a client’s session record.
A returning client needs the same stable, unique identifier to request its saved record. The identifier names a session and does not prove who connected.
Boiler example: Bex keeps the valve’s client ID stable when it reconnects to request its saved command subscription.
Also see: session state, persistent session, Authentication
Decoupling
Separation that lets listeners join without changing the sensor’s destination list.
Adding a listener changes the broker’s subscriptions rather than the sensor’s destination list. Sending and receiving applications still need to agree on topic names and payload meaning.
Boiler example: A new screen subscribes using the agreed topics and permissions.
Also see: Publish-subscribe, Topic, Payload
delay cap
A delay cap limits each individual retry wait.
It does not limit the sum of waits or the time spent attempting connections. Apply it by choosing the smaller of the growing delay and the cap.
Boiler example: Bex caps each wait in the boiler sensor’s retry schedule while measuring recovery at the dashboard separately.
Also see: backoff, exponential backoff, retry budget
exponential backoff
Exponential backoff doubles the base wait for each later retry in the chapter’s example.
Calculate the growing delay before applying any limit on an individual wait. The sum of waits leaves out connection work and does not measure when the receiver gets a reading.
Boiler example: Bex follows the sensor’s doubling retry waits separately from the time when the dashboard receives a boiler reading.
Also see: backoff, delay cap, retry budget
Fan out
Forward one publication to its matching subscribers.
The broker forwards a publication to the matching subscribers rather than requiring the sensor to send separately to each listener. Matching predicts the audience, but actual receipt still needs a subscriber trace.
Boiler example: Both the operations screen and alarm service receive the boiler publication.
Also see: Broker, Publish-subscribe, Subscriber
idempotent command
An idempotent command preserves the requested result when repeated.
A desired setting can preserve the result on repetition, while a toggle changes it again. A completed message exchange still needs a device reply or state check to prove the outcome.
Boiler example: Bex checks that repeating the shut-off command preserves the intended valve state and verifies the reported result.
Also see: QoS, PUBACK, observability
jitter
Jitter varies retry waits so devices need not retry together.
Growing waits and a cap determine wait sizes, while variation changes how devices’ retry times line up. Repeating the same fixed variation does not demonstrate independently random schedules across devices.
Boiler example: Bex varies the house devices’ retry waits to spread their attempts to restore the reading and command paths.
Also see: Backoff with jitter, backoff, delay cap
JWT
A JSON Web Token, or JWT, carries claims that a configured broker checker must verify.
The checker must verify how the token was signed, who signed it, its intended audience and its expiry. Putting a token in a password field alone does not enforce those checks.
Boiler example: Bex checks that the broker verifies the sensor’s token before accepting its claimed identity.
Also see: Authentication, Authorization, least privilege
Last will
Configured status the broker can publish after unexpected connection loss.
The client configures status that the broker can publish after an unexpected connection loss. That status is evidence about the connection rather than a fresh temperature or a complete fault diagnosis.
Boiler example: The boiler client’s lost connection can produce status rather than a new temperature.
least privilege
Least privilege means granting each device only the topic access required for its function.
Permission to read a topic does not grant permission to write it. A valid login must still be denied actions outside its allowed routes.
Boiler example: Bex permits the boiler sensor to send readings without granting it permission to send shut-off commands.
Also see: Authorization, Access-control list, Authentication
load balancer
A load balancer distributes client connections across broker nodes, which are separate broker instances.
Moving a connection to a healthy node is only part of recovery. Tests must also cover the subscriptions and waiting messages that the chosen service promises to keep.
Boiler example: Bex tests that boiler readings reach the dashboard after its connection moves away from a failed broker node.
Also see: Broker, session state, observability
local buffer
A local buffer is storage on the publishing device for messages it cannot yet send.
That storage needs a limit and a policy for what happens when it fills. The broker’s session settings cannot collect readings that have not crossed the broken connection.
Boiler example: Bex stores unsent boiler readings on the sensor while it cannot reach the broker.
Also see: Publisher, persistent session, session state
message expiry
Message expiry limits how long a message remains useful for delivery.
A message is discarded if the subscriber remains offline beyond its expiry interval. Choose that interval according to whether the old reading or instruction would still be useful on return.
Boiler example: Bex checks whether an old boiler reading should still be delivered when the dashboard returns.
Also see: Message Expiry Interval, Stale, Session Expiry Interval
Message Expiry Interval
Message Expiry Interval sets how long a publication remains valid.
It limits the useful delivery window of a message. Session Expiry Interval separately limits how long the broker keeps the client’s session record.
Boiler example: Bex chooses a delivery window for the rare too-hot alarm rather than assuming it remains useful forever.
Also see: message expiry, Session Expiry Interval, Stale
MQTT
MQTT, short for Message Queuing Telemetry Transport, is a set of agreed rules for exchanging messages.
MQTT lets devices and applications exchange messages through a broker, using topics. The devices and applications still decide what the message data means.
Boiler example: Bex follows a boiler temperature reading through the broker to the dashboard.
Also see: Publish-subscribe, Broker, Publisher
mutual TLS
Mutual TLS checks the client’s certificate and proof that it holds the matching secret key, as well as checking the broker’s identity.
The broker validates the client certificate, and the client must protect its secret key. The checked identity still needs limits on which topics it may use.
Boiler example: Bex checks the boiler sensor’s certificate separately from its permission to send readings.
Also see: TLS, certificate, Authentication, Authorization
network loop
A network loop processes MQTT network work and passes incoming messages to the functions that handle them.
Stopping the loop leaves incoming work unprocessed. A working loop, the right subscription and an available message handler are separate requirements to check.
Boiler example: Bex checks that the dashboard keeps its network loop running while waiting for boiler readings.
Also see: callback, subscription, packet
observability
Observability means using signals from the broker and receiving applications to locate failures, delays and stale data.
Healthy connection counts can coexist with growing queues and old readings. Monitor waiting-message counts and ages alongside stale readings and unconfirmed command results.
Boiler example: Bex checks the age of boiler readings and the valve’s reported result alongside connection health.
Also see: Stale, Broker, idempotent command
packet
A packet is a unit of data sent on the network.
An MQTT publication packet carries the topic used to route the message, the useful message data and fields controlling its handling. Counting only the useful data misses the space used by the other fields.
Boiler example: Bex examines the boiler reading’s route name and control fields alongside its temperature value.
Payload
The content carried by a message.
The payload supplies the message’s content, such as a temperature value and unit. Matching the topic does not check whether that content is current or follows the application’s format.
Boiler example: 83.4 C is the content of the boiler reading.
persistent session
A persistent session keeps subscriptions and eligible pending messages so a client can resume after a break.
Pending delivery depends on the session surviving, the messages remaining valid and the queue staying within its limits. The broker cannot store new readings that an offline sensor has never sent.
Boiler example: Bex tests whether the returning valve receives a still-valid shut-off command from its saved session.
Also see: session state, client ID, Session Present, message expiry
PUBACK
PUBACK is the reply that confirms the sender-to-broker exchange for a QoS 1 publication.
It does not show that the dashboard received or decoded the value. The receiver’s own output is needed to establish receipt there.
Boiler example: Bex checks the dashboard’s received boiler reading separately from the sensor’s PUBACK reply.
Publish-subscribe
A sender publishes messages and receivers subscribe to the messages they need.
The sender sends to a broker rather than addressing every receiving application. Receivers register the topics they want, so another listener can join without changing the sensor’s destination list.
Boiler example: The boiler sensor sends one reading for the screen and alarm service.
Also see: Publisher, Subscriber, Broker
Publisher
A client that sends a topic and payload to the broker.
The publisher names the route and supplies the message content. It sends to the broker rather than contacting each operations screen or alarm service directly.
Boiler example: The boiler sensor publishes its temperature reading.
QoS
Quality of service, or QoS, is the chosen delivery level for an MQTT exchange.
The exchange from sender to broker is separate from the exchange from broker to receiver. A completed exchange does not prove that a device carried out a command.
Boiler example: Bex checks the shut-off valve’s reported state as well as the command’s delivery exchange.
Also see: MQTT, PUBACK, idempotent command
Retained message
A last-known snapshot stored for a topic that a new matching subscription can receive.
Retained state belongs to a topic and can supply a last-known value to a new matching subscription. The receiver still needs a timestamp or age to judge freshness; a snapshot is not a complete history.
Boiler example: A late operations screen can receive the stored boiler temperature.
retry budget
A retry budget limits attempts across the period covered by the recovery policy.
Its counter must survive repeated calls, and the policy must specify what happens when the budget runs out. A local counter that resets on every call cannot provide that continuing limit.
Boiler example: Bex checks that the boiler sensor’s retry count survives calls and that its policy defines what happens when attempts run out.
Also see: backoff, delay cap, exponential backoff
Session
Client-related state such as subscriptions and eligible queued messages.
Session state belongs to a client rather than to a topic. Its settings and the broker’s limits determine which eligible messages can wait while that client is offline.
Boiler example: Session settings affect what may wait while a boiler listener is offline.
Also see: Retained message, Subscriber, Broker
Session Expiry Interval
Session Expiry Interval sets how long MQTT 5 keeps session state after a disconnection.
The default keeps no session state after disconnection. A positive interval must have been agreed before the client goes offline for its session to survive that absence.
Boiler example: Bex sets the lifetime of the valve’s saved session separately from the useful lifetime of a shut-off command.
Also see: Clean Start, session state, Message Expiry Interval
Session Present
Session Present is the flag in the broker’s connection reply that reports whether stored session state was found.
On a successful connection, the flag confirms whether the client resumed saved state. A new session requires the client to restore the subscriptions it needs.
Boiler example: Bex reads Session Present when the valve reconnects before relying on its previous command subscription.
Also see: client ID, Clean Start, persistent session
session state
Session state is the broker’s record for a client, including its subscriptions and messages eligible to wait for delivery.
Whether the record survives a disconnection depends on the session rules and broker settings. A stored topic value for new listeners is kept separately.
Boiler example: Bex checks whether the broker kept the valve’s command subscription while the valve was offline.
Also see: Session, persistent session, Retained message
Stale
Too old for the reading’s intended use.
A reading can arrive now even though it was measured too long ago to be useful. Check its timestamp or age before displaying retained or delayed values as live.
Boiler example: Receiving an old boiler temperature now does not make it a new measurement.
Also see: Retained message, Payload, Telemetry
Subscriber
A client that requests messages through a topic filter.
The subscriber registers a topic filter with the broker to describe the messages it wants. A matching filter still needs permission, and a subscriber trace is needed to show actual receipt.
Boiler example: The operations screen asks for boiler temperature messages.
Also see: Topic filter, Access-control list, Broker
subscription
A subscription is a client’s request to receive messages matching a topic.
The broker compares published topic names with the client’s registered matching pattern. Matching a route and having permission to receive its messages are separate checks.
Boiler example: Bex checks that the dashboard’s subscription matches the boiler temperature topic.
Also see: Subscriber, Topic filter, Authorization
Telemetry
Remote readings and status messages.
A sensor can send a remote temperature reading to an operations screen. The value needs its source, unit and meaning to be clear to the receiving application.
Boiler example: The boiler sensor sends temperature readings to the operations screen.
TLS
Transport layer security, or TLS, protects the connection between a client and the broker.
The client must validate the broker’s certificate, including its hostname. Protecting the connection does not decide which topics a client may read or write.
Boiler example: Bex checks the protected sensor connection separately from permission to publish boiler readings.
Also see: certificate, Authentication, Authorization
Topic
The name used to route a message.
A topic identifies the source and signal so a receiver can ask for the reading it needs. The topic names the route while the payload supplies the value.
Boiler example: plant/boiler7/temperature names the boiler reading.
Also see: Topic level, Topic filter, Payload
topic alias
A topic alias is a short value established for a topic name so later publications can omit the repeated name.
The mapping must be established before later messages can use it. It reduces repeated name bytes without changing the delivery level or saved-message rules.
Boiler example: Bex establishes an alias for the boiler temperature topic before sending later readings with it.
Topic filter
A request describing which topic names a subscriber wants.
The broker compares the publication’s topic name with the subscriber’s filter. An exact filter must agree with the name; wildcard filters can select several topic names.
Boiler example: plant/+/temperature requests temperature readings from matching boilers.
Also see: Topic, Wildcard, Access-control list
Topic level
One part of a topic name separated by slashes.
Slashes divide a topic name into parts that can identify the source and signal. Compare these parts with the filter before inspecting the payload value.
Boiler example: boiler7 is a level in plant/boiler7/temperature.
Also see: Topic, Topic filter, Wildcard
Wildcard
A filter symbol that can match more than one topic name.
In a topic filter, + matches one level and a final # matches the rest of a branch. A broad filter can include unrelated signals and does not replace topic permissions.
Boiler example: The screen uses + for one level; the alarm service uses a final # for the branch.
Also see: Topic filter, Topic level, Access-control list