October 2, 2025 - MQTT Service Java client SDK is replaced by direct Messaging Service connections

Context


Change Type: Preview
Product area: Platform services
Component: MQTT
Deployed at: eu.latest.cumulocity.com, apj.cumulocity.com, jp.cumulocity.com, cumulocity.com, us.cumulocity.com, emea.cumulocity.com

Technical details

Build artifact: mqtt-service (0.9.21)

Description


Caution
This change only affects the new Cumulocity MQTT Service capability.

The existing Cumulocity Core MQTT capability is not affected.

Preview
This feature is in Public Preview and may be subject to change in the future.

As previously announced, when the Cumulocity MQTT Service transitions from Public Preview to General Availability (GA), the MQTT Service Java client SDK will no longer be supported.
Instead, microservices and external applications (clients) that need to exchange messages with MQTT devices connected to the MQTT Service will connect directly to the Cumulocity Messaging Service using the Apache Pulsar client protocol.
Direct Messaging Service connectivity for MQTT Service clients is now available as part of the MQTT Service Public Preview.

All microservice and external application clients currently using the MQTT Service Java client SDK should migrate to the Pulsar client protocol as soon as possible.
Detailed documentation of the requirements, conventions and best practices for connecting Pulsar clients to the Messaging Service is available, along with example code for an external client.
Further examples will be published before the MQTT Service GA date.

Impact on clients using the MQTT Service Java client SDK

The MQTT Service Java client SDK is deprecated but will remain available and supported until the MQTT Service GA date.
Clients can continue to use the Java client SDK in parallel with direct connections to the Messaging Service until then.
MQTT messages published by connected devices will be delivered to both Java client SDK clients and directly connected clients.
Messages published to an MQTT topic by either type of client will be delivered to connected devices that are subscribed to that topic, subject to device-level isolation constraints.