Today is a great day for the Camunda Spring Boot starter extension: after three month of hard (but mostly fun) work, we are proud to announce the release of 2.0.0.
We decided to switch to a new major version, because a lot of things changed:
- new groupId:
org.camunda.bpm.extension.springbootand a new maven module structure
- switch to Java 8
- switch to Spring Boot 1.4.2
- switch to Camunda BPM 7.6.0
Besides those internal enhancements, we worked on stability, convenience and support of the enterprise edition.
We are happy to announce the Camunda Modeler version 1.5 release!
This release adds the ability to model Decision Requirement Diagrams (DRDs). On top of that, it brings huge performance improvements when working with large diagrams (BPMN, CMMN and DMN) and feature parity with Camunda BPM 7.6.
The future of the Activiti Open Source project is currently uncertain. Camunda split from the Activiti project in 2013. Since then, we maintained our own open source fork of the original Activiti Codebase.
The objective of this post is to illustrate the diverging directions the two projects have taken and to serve as input for users who now consider migrating from Activiti to Camunda. The first part focuses on two key topics: core BPMN Execution and the persistence layer. For me, after all the feature talk and the marketing-hurrah is said and done, BPMN and persistence is where the meat is. In the second part, I compare the current state of the Camunda codebase to the (unreleased) Activiti 6.
With the Activiti Core Developers having left Alfresco (the company behind Activiti), the future of the Activiti project is quite questionable. More and more Activiti users want to migrate to Camunda. There are actually very goood reasons to do so, see 5 Reasons to switch from Activiti to Camunda and Camunda Engine Evolution since Activiti Fork.
Camunda is a fork of Activiti. We actually developed big parts of the engine ourselves before we decided to part ways with Alfresco back in 2013. Hence it is relatively easy to migrate. This post lists the necessary steps to achieve this:
Camunda 7.6.0-alpha5 is here and it is packed with new features. The highlights are:
- Implementation of the BPMN Conditional Event
- Batch Cancellation of Historic Process Instances
- Huge performance improvements due to caching of Scripting Engines and Compiled Scripts in DMN Engine
- Expressions in Signal and Message Event Names
- Cockpit Usability Improvements
- Pluggable Deployment Cache
- 10 Bug Fixes
The complete release notes are available in Jira.