MQTT

Solace PubSub+ event brokers support the OASIS MQTT 3.1.1 standard to meet the needs of connected devices and mobile applications that need an efficient way to send and receive information that requires very little bandwidth, client-side processing power and/or bandwidth. The Solace PubSub+ event broker works with any third-party MQTT 3.1.1 compliant client API, including open source APIs available through Eclipse initiative called Paho.

Transports

Solace PubSub+ event brokers support the following transports for the MQTT service:

  • Plain-Text
  • SSL
  • WebSocket
  • WebSocket Secure

IPv4 and IPv6

MQTT clients can connect to a Solace PubSub+ appliance using IPv4 or IPv6. To connect using IPv6, the appliance's message-backbone needs to be configured with an IPv6 global unicast or unique local address. For more information on configuring appliance IP interfaces and addresses, refer to Configuring Appliance IP Interfaces.

MQTT Component Concept Map

If you haven't used MQTT and Solace PubSub+ together before, you might want to look at the MQTT section of the Component Concept Maps page. It'll take you on a tour of the PubSub+ event broker's messaging components, and explain at a high level how they make data move from producers to the broker, and from the broker to consumers, with MQTT.

Get Started with MQTT Messaging Tutorials

These tutorials will introduce you to the fundamentals of using MQTT to develop applications using the Solace PubSub+. They cover common messaging requirements such as pub/sub, message persistence, request/reply, and more.

Start Tutorials