Our latest release of Camunda 7 focuses on our commitment to supporting Jakarta EE 10. We’ve implemented several customer-requested improvements to make maintaining and operating Camunda 7 applications easier.
These updates and new features are vital to ensure the long-term maintainability of Camunda 7, and allow for continued support until 2027 and extended support agreements until 2030.
Navigating the Jakarta EE transition can be a bit challenging, especially regarding compatibility. Our primary goal was to strike the right balance between innovation and stability. By embracing both .javax and .jakarta namespaces, we wanted to give you more flexibility in adopting Jakarta EE on your timeline.
With this release, we’re thrilled to announce official support for Camunda components to kickstart their projects using Spring Boot, Wildfly, or Quarkus with minimal effort. This support paves the way for you to harness the latest features and capabilities more easily.
Read our blog post on our transition to Jakarta 10 to understand our approach better.
Developers overwhelmingly choose Spring Boot as their preferred environment for building Camunda applications. With the end of open-source support for Spring Boot 2.7 in November of this year, we prioritized Spring Boot 3.1 support to ensure that developers have seamless access to the latest version. Check out the Spring Boot update guide to migrate your applications from Spring Boot 2.7
We’ve eliminated all dependencies on the deprecated JBoss Modular Service Container, which has been obsolete since 2016 and is no longer part of the Wildfly 29 ecosystem.
We’re excited to announce that support for the latest Quarkus 3 version. For a comprehensive list of all the new features and changes, please read their Quarkus 3 release blog post. You can find more details about the extension on our dedicated Quarkus Integration page.
Early consideration of historic data clean-up is crucial to mitigate potential performance bottlenecks in Camunda 7. Often, performance issues stem from an excess of data in the database, a problem that can be traced back to a lack of planning for job clean-ups during the initial phases of automation projects.
In our latest release, we’ve proactively addressed this challenge. We’ve activated a clean-up job and made it mandatory for developers to specify the History-Time-To-Live (HTTL) property for each BPMN or DMN diagram.
The default HTTL in Desktop Modeler is predefined at 180 days, and it will issue warnings if left empty. Diagrams lacking HTTL definitions will not be accepted. However, you can deactivate the mandatory property, giving you the flexibility to tailor clean-up intervals to specific requirements or adhere to their existing deployment practices.
This empowers you to maintain an optimized and efficient Camunda environment.
We’ve taken significant steps to streamline data cleanup for faulty process instances that can cause production bottlenecks. Sometimes, a bug can inadvertently generate an excessive number of activity instances within a newly deployed process, leading to performance slowdowns or make the system unresponsive.
You can now address this issue without the need for direct database-level interventions. In the past, configuring removal times for such instances was always one database transaction that frequently led to timeouts when dealing with a large volume of process instances. Our latest enhancement introduces a removal time batch operation that allows you to set removal times in manageable chunks.
This new feature ensures you can set the removal time without causing transaction timeouts. Combined with the clean-up job, it allows you to safely remove high quantities of data from the database and bring the system back to nominal performance levels.
This is just a short list of features that customers have requested. If you’d like to see the full list, check out the release notes or posts for alpha releases below.
Share Your Thoughts with Us!
Your feedback is really important to us, so please download the latest release of Camunda 7, try it out, and let us know what you think!.