Your hosts for today
Do you already use Camunda?
No answer; 45; 8%
Not at all; 166; 32%
we're evaluating; 174; 33%
we're developing; 83; 16%
we're in production; 58; 11%
Why do you use Camunda?
•Executes BPMN 2.0
•Best option for Java
•is Open Source
•Stanardized technologies and Skills
•Easier, quicker development
Also trusted by:
Camunda 7.2 Statistics
April 1st –Nov 30th
~ 1,700 person days
Features; 209; 33%
Bugs; 203; 33%
Tasks; 211; 34%
Performance / Scalability
•Camunda BPM is increasingly used in High-Load Situations
•A „high-load situation“ starts at ~10 instantiated processes per Second
•Some Customers run Camunda with > 1,000 Process Instances per Second
•This means we continuously improve the performance and scalability
•Execute process instances in a short amount of time
•Support load balancing in Clusters
•Prepare Camunda for alternative storage strategies (No SQL, In Memory etc.)
Camunda 7.1 (!) compared to JBoss jBPM 6
More Information: http://camunda.com/landing/whitepaper-camunda-jbpm
In our tests, Camunda‘s throughput was 10x –30x higher than with JBoss jBPM.
Performance Improvements in 7.2
•Improved First Level Cache (throughput increased by up to 90%)
•Improved Load Balancing for Cluster Mode
•Log Level for History can be configured
•Minimize Risk of Deadlocks in High-Load Situations
In collaboration with
“The tasklist is the central point of contact for business users with the BPM platform and is therefore an essential component. The innovative implementation of the Camunda tasklist matches the DAB bank's web technology stack perfectly and saves extensive in-house development. The functionality is optimally aligned to the Camunda BPM platform and due to its flexible adaptability also fulfills the needs of a bank.
Karl Brandner, Chief Architect
Your own Setup?
Your very own HTML 5 User Interface
•Greatly simplifies the implementation of task forms.
•You can directly bind Html form controls to process variables.
•The Forms SDK handles the fetching of the variable values from the process engine, type conversions and so on.
•The Forms SDK optionally integrates with AngularJSto take advantage of AngularJS form validation and other AngularJS goodies.
Death by Property Panel
Zero-Code BPM Suites
Java Objekte in XML or JSON serialisieren
XML or JSON
•Anyone can directly inspect Java objects in the database and Cockpit
Improved Handling of Data Formats
XML or JSON
•Directly access XML or JSON within the process via APIs
•No need to convert XML or JSON into Java Objects
Why Scripts and Templates are awesome
•No Java Code / Classes needed
•(Re-)deployment during runtime
•Can be versioned as part of the process definition
•Can be embedded inside the BPMN as well as referenced and maintained in standalone files
•Great performance thanks to compile & cache
•Simple API for implementing Connectors as reusable Components
•Included with Camunda 7.2: SOAP and REST (both based on Apache HTTP Client)
•Fundamentally different approach than Zero-Code Suites:
•Developer become more productive –it‘s not about „empowering Business Analysts“
•However not every developer speaks Java
•Primary Target Group: IT divisions that want to provide a workflow infrastructure for their organization (other IT teams)
•Focus on API instead of Properties
•Connectors can be used in different components, e.g. Java Delegates
A powerful combination
Example: Do I have to work today?
Simple REST Call
Start with Process Variable date
(e.g. via unit test)
Invoke REST Service that provides holidays as JSON
Route based on holiday
More in the Documentation
•Connectors: http://docs.camunda.org/latest/guides/user- guide/#process-engine-connectors
•Scripting: http://docs.camunda.org/latest/guides/user- guide/#process-engine-scripting
•Data: http://docs.camunda.org/latest/guides/user-guide/#data- formats-xml-json-other
•Published by OMG in May 2014 as the BPMN-equivalent for „Cases“
•Targets „Activities that are not so predefined and repeatable, but instead depend on evolving circumstances and ad hoc decisions by knowledge workers regarding a particular situation, a case (see Davenport 1994 and 2005; and Van der Aalst 2005)”
•Typical Use Cases:
You often have both
„Review Invoice“ as a simple Case
Human Taskthat will be created when the Case is created
Completing the Task triggers Completion of the Case
Milestone, that will be reached depending on the outcome of the Task
That maybe created by the knowledge worker
Process Task, that maybe created by the knowledge worker
How can I move ahead?
Open Source Edition
•Docs, Tutorials etc.
•Support, Patches etc.
Contact: Germany +49 30 664 04 09 00 | US +1.415.800.3908