Camunda BPM Telemetry: Community FAQ
Camunda BPM version 7.14 includes the option to turn on Telemetry as explained in this earlier blogpost. This anonymous data will be used to help us better understand what people are really doing with the engine and will make it easier for us to highlight the community influence on future roadmaps. When any of us stakeholders bring new potential features to the table for an upcoming release, our opinion on its own isn’t enough to shift the roadmap. Any good proposal needs to be data-driven. At the moment, a lot of the data I bring along with my proposals comes from forum posts, individual requests on JIRA, and one-on-one conversations with community members at user groups or other events. This...
Highlights from the Summer Hackdays 2020
The Camuda hackdays are a wonderful time of year where the people in the company who like to code spend about three days working on their own fun passion projects, either in a team or by themselves. These projects have often become the catalyst for new features and community extensions. This year we had more people than ever joining for the hackdays and of course for the first time we did it fully remote! Supported by a lovely care package from the wonderful Camunda backoffice team. Hence all the lovely hats in the pictures below! More than 20 teams gathered together. At the end of the three days we got to watch each team present their project. The kinds of...
How CMMN never lived up to its...
Even before the Object Management Group (OMG) had released the CMMN Specification in 2014, Camunda had already started building a CMMN engine. In the years that followed, we invested in symbol support, modeling capabilities, and admin tools. But after a couple of years, we decided that we would not be adding any more CMMN features to Camunda and that it will simply be maintained but not fully supported. This post is about the experience Camunda and its Community had with the CMMN standard and how this led to the choices we made to first embrace and then distance ourselves from CMMN. The Promise of CMMN Case Management Model and Notation (CMMN) was introduced as a direct result of the massive...
Camunda’s Evolution: An Open, Distributed Platform
We have recently released the first iteration of the OpenAPI documentation, which is a big step towards making Camunda a more technology independent platform. The journey up until now is very much worth discussing. Camunda started off as a lovely, lightweight java project, which was intended to be used by Java developers to embed in their projects so that they could orchestrate their processes. As far as this mission statement goes – it was, of course, a great success. The features we created focused on the Java ecosystems and the needs of Java developers, which is obvious considering that our community was almost exclusively made-up of Java folk. There came a time, one which I assume happens often for open...
The Collaborative Community of BPMN enthusiasts
This month 10 years ago, BPMN 2.0 was finalized and adopted as a standard, which in itself is something Camunda is happy to celebrate.But what has happened in the BPM space in the meantime is probably the most interesting thing about BPMN 2.0. A whole ecosystem and community has grown from the standard. While it originally came into existence to give the process building community a unified language, it sparked a lot of independent innovation. This was because turning a visual process language into an executable framework brought in a lot of new ways of thinking about processes, so modelers, engines and reporting tools began springing up – all around the same standard. So 10 years on we’ve arrived at...
Camunda Release Highlights
In the past few days, months of work by my fellow Camunda folk has resulted in a cavalcade of new releases – from big stuff like: Camunda BPM 7.13.0 Camunda Modeler 4.0.0 Camunda Optimize 3.1.0-alpha2 To smaller project releases External Task Client 2.0.0 for NodeJS Assert 6.0.0 Spring Boot Starter 7.13.0 Because all of this fast-paced release of software can be slightly overwhelming, I wanted to spend some time focusing on a few specific parts that I’m quite excited about.
How to choose the right Camunda architecture.
Decide on the Granularity of your orchestration. Probably the most important choice you need make about how to use camunda revolves around the level at which you want to orchestrate. You could also think of level as the granularity at which camunda will operate and this often is directly related to the complexity of the communication to what you want to orchestrate. The choice you make here will directly impact how deployment works, how best to maintain your system, error handling and even performance – so it deserves careful thought.
Camunda Question Corner 1
One of the things I enjoy the most, as part of the Developer Relations team, is meeting people from the community who I can talk to about all the lovely nerdy Camunda stuff that inhabits my brain. This usually involves traveling to meetups and conferences – which is usually great but considering I’m grounded in Berlin for a while, it’s no longer an option. Which is why we thought it would be a good idea to set up a little virtual space where I can make people listen to me ramble on about Camunda stuff.
Enterprise Platform for Workflow and Decision Automation