MQTT

Solace PubSub+ message 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+ message broker works with any third-party MQTT 3.1.1 compliant client API, including open source APIs available through Eclipse initiative called Paho.

Solace PubSub+ message brokers support the following transports for the MQTT service: Plain-Text, SSL, WebSocket, and WebSocket Secure.

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.

Get Started with MQTT Messaging Tutorials

Tutorials are provided on the Solace Developer portal to 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.