Hi. When migrating from, for instance, Camunda 8.7 to Camunda 8.8, must job workers written in Java be migrated as well? The Java SDK has its own versioning cycle, but are the these versions peculiar to a Camunda version or not?
Thanks for answering.
The Java SDK versioning generally aligns with Camunda platform versions, but you can use newer SDK versions with older clusters and vice versa, with some exceptions. I found the following relevant resources:
Does this help? If not, can anyone from the community jump in? 
Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process. 
Hello,
Migrating from Camunda 8.7 to 8.8 does not immediately require changes to Java job workers.
Starting with Camunda 8.8, the new unified Camunda Java Client (CamundaClient) was introduced to replace the previous ZeebeClient. However, the existing ZeebeClient classes are still present for backward compatibility. They are currently marked as deprecated, but they continue to work because they are effectively relocated to the new Camunda client implementation.
Since these APIs are deprecated and planned to be removed in a future release (currently targeted around Camunda 8.10), it is recommended to plan a migration to the new Camunda Java Client SDK. Migrating will ensure long-term compatibility and allow you to benefit from the latest features and improvements introduced with the unified client.
Thanks Tarek. Very clear.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.