Overview

Every NEXT application that requires an MQTT broker for communication with clients can utilize an MQTT instance provided by the NEXT platform.
Each instance is isolated from other NEXT applications, ensuring no data mix-up between different NEXT applications. Applications are free to use topics as desired without the need for prefixes or suffixes.

Client Connections

Communication with clients can be established through a standard MQTT connection over TLS or via websockets using a unique URL endpoint or IP on standard ports. Each NEXT application will receive a dedicated endpoint where only the related clients will connect.
Various authentication and authorization options for these clients are available.

For more information about client connections, please click here.

Application Access

Services running in the NEXT cloud environment can communicate with the MQTT broker either directly using an MQTT client connection described here, or through a KAFKA Bridge that relays incoming and outgoing MQTT messages to KAFKA topics, as detailed here.

Authentication and Authorization

Besides authentication with client certificates, client authentication and authorization are not managed directly within the MQTT broker but must be implemented on the customer’s side. For more details, please read here.