Copyright © by HiveMQ. All Rights Reserved.

Speaker

Based out of Chicago, Mary is a Java

Champion and President and Executive
Board Member of the Chicago Java Users
Group (CJUG). She is also the co-organizer
for several meetup groups such as, the
Data, Cloud and AI In Chicago, Chicago
Cloud, and IBM Cloud Chicago.

Mary Grygleski She has extensive experience in product

Senior Developer Advocate at HiveMQ and application design, development,
integration, and deployment experience, and
@mgrygles specializes in Reactive Java, Open Source,
https://www.linkedin.com/in/mary-grygleski/ and cloud-enabled distributed systems.
https://www.twitch.tv/mgrygles
https://discord.gg/RMU4Juw

Copyright © by HiveMQ. All Rights Reserved.

 ❏ The IoT Stack
❏ What is MQTT?
❏ A bit of a history
❏ OASIS open standard, community-driven protocol
❏ MQTT 3.1.1 Features

AGENDA ❏
❏ MQTT 5.0 Features
Use Cases for MQTT
❏ Alternative Protocols for IoT
❏ Summary - Why MQTT is the top choice
❏ Demo
 From 30,000 Feet: The IoT Stack

Consumer Enterprise Industrial

Solutions (Manufacturing,
(Home, Lifestyle, Mobility, (ERP, Marketing, Sales, Automotive, Logistics,
Entertainment…etc.) Business Ops…etc.) Construction…etc.)

Cognitive Platform Interactions (spoken, gestures), AI, Voice Recognition…etc.

Services (Geospatial, Recommendations), Reports, Events, Machine Learning,

Analytics Platform Stream Processing…etc.

IoT Messaging Middleware, Protocol Gateway, Data Aggregation, Data

Core Platform Storage/Filter

MQTT, CoAP, AMQP, DDS, XMPP, IPv4, IPv6, 6LoWPan,Bluetooth, GSM, Modbus,
Communication Protocols BACnet

Devices & Components: Smart Devices, Sensors & Actuators, Embedded

Devices Devices…etc.

Copyright © by HiveMQ. All Rights Reserved.

 What is MQTT?
• A standard binary publish-subscribe messaging protocol designed for fast and reliable data transport between
devices especially under very constrained conditions
• Constraints include unreliable network connectivity, limited bandwidth, limited battery power, and so on

• Built on top of TCP/IP

• Ideal for the Internet of Things

Copyright © by HiveMQ. All Rights Reserved.

 A Brief History of MQTT

• Invented in 1999 by Andy Stanford-Clark at IBM and Arlen Nipper at what was then
Arcom - and now Cirrus Link
• Prompted by the need to design a protocol that could handle a very limited operating
environment that can afford only minimal battery loss and minimal bandwidth to
connect with oil pipelines via satellite

Copyright © by HiveMQ. All Rights Reserved.

 History… 1999
invented
for oil pipeline
monitoring
2010
MQTT 3.1 opened as royalty free protocol

2012
Mosquitto 1.0 released

2013
HiveMQ 1.3 released

2013
OASIS TC formed

Copyright © by HiveMQ. All Rights Reserved.

 History…
2014
MQTT 3.1.1 officially released

2018
MQTT 5 officially released

2018
HiveMQ 4 has MQTT 5 support

Copyright © by HiveMQ. All Rights Reserved.

 THE MQTT Technical Committee

Copyright © by HiveMQ. All Rights Reserved.

 MQTT Overview

● IoT Messaging Protocol

● 3 QoS Levels

● Retained Messages

● Stateful - persistent sessions

● Binary with minimal overhead

Copyright © by HiveMQ. All Rights Reserved.

Basic Features of
MQTT 3.1.1
 Publish / Subscribe

Connect
Connect ACK

Subscribe MQTT
MQTT
Server
Client SubscribeACK (Broker)
Publish

Publish ACK

Copyright © by HiveMQ. All Rights Reserved.

 CONNECT / CONACK

Copyright © by HiveMQ. All Rights Reserved.

 WILL
● Client defines Will (LWT)
● Broker sends this message if this client dies
● It is a real Push
● Useful to implement on / off mechanism in a safe way
● message when Subscribing to the topic

Copyright © by HiveMQ. All Rights Reserved.

 Publish / Subscribe

Copyright © by HiveMQ. All Rights Reserved.

 Retained Message

● Last Known “Good Value”

● Last message will be stored on broker side
● Client decides if a message is retained or not
● Future Clients get the retained message when
Subscribing to the topic

Copyright © by HiveMQ. All Rights Reserved.

 Quality of Services

Copyright © by HiveMQ. All Rights Reserved.

 Quality of Services 0

Copyright © by HiveMQ. All Rights Reserved.

 Quality of Services 1

Copyright © by HiveMQ. All Rights Reserved.

 Quality of Services 2

Copyright © by HiveMQ. All Rights Reserved.

 But, where is MQTT 4 ?

Hint: let’s look at the CONNECT message packet detail

for MQTT 3.1.1:

Copyright © by HiveMQ. All Rights Reserved.

 MQTT 5

Copyright © by HiveMQ. All Rights Reserved.

 MQTT 5 - Overview

● Successor of MQTT 3.1.1

● Non-backward compatible

● First public release in January 2018,

official release in March 2019

● Many new features

● Clarifications of the 3.1.1 specification

Copyright © by HiveMQ. All Rights Reserved.

 MQTT 5 - Goals

• Enhancements for scalability and large scale

systems

• Improved error reporting

• Formalize common patterns including capability

discovery and request response
• Extensibility mechanisms including user properties

• Performance improvements and support for small

clients

Copyright © by HiveMQ. All Rights Reserved.

 NEW FEATURES

Copyright © by HiveMQ. All Rights Reserved.

 Session & Message Expiry

• Session Expiry is an optional part of the CONNECT

message

• Session Expiry Interval in Seconds

• Broker expires session after the given interval as soon as

the client disconnects

• Publication Expiry interval is an optional part of a PUBLISH

message
• Applies to online and queued messages

Copyright © by HiveMQ. All Rights Reserved.

 User Properties

• User Defined Metadata Headers

• Can be part of most MQTT packets (CON, PUB, SUB)

• UTF-8 encoded Strings

• An unlimited number of user properties can be added

Copyright © by HiveMQ. All Rights Reserved.

 Shared Subscriptions Special Syntax: $share/{ID}/my/topic

• Useful for scaling out backend subscribers

• Client Load Balancing. Multiple clients share the

same subscription

• Also supported by HiveMQ for MQTT 3.1 and MQTT 3.1.1

• Up-/Downscaling of clients at runtime possible. Perfect for

cloud native scenarios (Kubernetes, …)

• Optional feature, not supported by all vendors*

* HiveMQ fully supports all optional features, including this feature

Copyright © by HiveMQ. All Rights Reserved.
 Shared Subscriptions

Copyright © by HiveMQ. All Rights Reserved.

 Request / Response Pattern for “business ACKs”

• The MQTT request-response pattern is not the same as the

request-response of synchronous, client-server based
protocols like HTTP.

• Request as well as responses are at least Topics and can have

more than one or no subscriber in MQTT.

• The Client must subscribe to a response topic prior to sending data.

• “Request Response Information” place for response topic

• “Correlation Data” header for correlation of the request and its

response

Copyright © by HiveMQ. All Rights Reserved.

 Request / Response

Copyright © by HiveMQ. All Rights Reserved.

 Lightweight and Bandwidth Efficient

• Every message works as a discrete chunk of data, opaque to the broker

• MQTT Control packet structure:
• Fixed header, Variable header, Payload
• Protocol headers are small in size:
• 2 byte fixed header
• up to 12 bytes of additional variable header (variable size and present only when
needed)

Copyright © by HiveMQ. All Rights Reserved.

 Data Agnostic

• Supports all kinds of data:

• images
• text in any encoding format
• encrypted data
• binary data

Copyright © by HiveMQ. All Rights Reserved.

 Continuous Session Awareness

• Persistent sessions
• Broker store messages when offline
• QoS level 1
• Retained messages
• Normal message with "retain" flag will be stored and sent to new
subscribers to its topic
• Last will and testaments
• Client can specify a message to send in case it disconnects ungracefully
• Very useful in IoT especially over unreliable networks

Copyright © by HiveMQ. All Rights Reserved.

 MQTT 5

• Introduction of semantic metadata like user properties, payload indicators, or

content type descriptors
• Request-response pattern
• Shared subscriptions
• Negative acknowledgments
• Message and session expiry per client
• More…

Copyright © by HiveMQ. All Rights Reserved.

 Use Cases for MQTT

• IoT
• Industrial IoT (IIoT)
• Industry 4.0
• Industry verticals:
• Automotive
• Logistics
• Manufacturing
• Energy
• Consumers:
• Smart Home
• Lifestyle

Copyright © by HiveMQ. All Rights Reserved.

 Alternative Protocols to MQTT

• HyperText Transport Protocol (HTTP)

• Constrained Application Protocol (CoAP)
• Advanced Messaging Queueing Protocol (AMQP)
• Object linking & embedding for Process Control - Unified Architecture (OPC-UA)
• Data Distribution Service (DDS)
• Extensible Messaging and Presence Protocol (XMPP)

Copyright © by HiveMQ. All Rights Reserved.

 Integration with Other Frameworks

● Streaming platforms: Apache Kafka

● Other MQTT Brokers: Mosquitto
● Runtimes - SpringBoot

Copyright © by HiveMQ. All Rights Reserved.

 Summary

• Simplicity - Pub/Sub - Asynchronous processing - Loosely coupled

• Lightweight
• Operating in a constrained environment
• Unreliable, high latency network
• Limited battery and other resources
• Ideal protocol for IoT use cases (other protocols such as HTTP would be too
heavy)

Copyright © by HiveMQ. All Rights Reserved.

Demo
 Resources

Get Started with MQTT

Evaluate HiveMQ Broker

MQTT Essentials Series

Try HiveMQ Cloud

MQTT at OASIS

Copyright © by HiveMQ. All Rights Reserved.

ANY
QUESTIONS?
Reach out to community.hivemq.com
THANK YOU

Contact Details

Mary Grygleski
[email protected]
https://www.linkedin.com/in/mary-grygleski/
@mgrygles
https://discord.gg/RMU4juw

https://www.twitch.tv/mgrygles