Context
Change Type: Announcement
Product area: Platform services
Component: MQTT
Technical details
Build artifact: mqtt-service
Description
Caution
This change only affects the new Cumulocity MQTT Service capability.
The existing Cumulocity Core MQTT capability is not affected.
What changes?
The Cumulocity MQTT Service Java client SDK is deprecated. It is being replaced by direct connections to the Cumulocity Messaging Service using the Apache Pulsar client protocol.
How does this change impact you?
Developers of microservices and external applications currently using the MQTT Service Java client SDK should prepare to migrate their clients to use direct connections to the Cumulocity Messaging Service. The new connection method will be made available very soon as part of the MQTT Service Public Preview and will be announced separately.
Backwards compatibility
The MQTT Service Java client SDK is deprecated effective immediately but will continue to work and be supported until the MQTT Service reaches General Availability (GA). Once the new method is available, it can be used in parallel with direct connections to the Cumulocity Messaging Service during the transition period. The SDK will be completely removed and will no longer be supported once the MQTT Service reaches GA. We recommend migrating to the new approach as soon as it becomes available.