In general, we may conclude that
Camunda performed better and
more stable for all metrics when
compared with WfMS A and WfMS B.
Micro-Benchmarking BPMN 2.0 Workflow Management Systems with Workflow Patterns,
June 2016, University of Stuttgart, Germany and University of Lugano, Switzerland
At Google, we have
Senior Architect at Google discussing BPMN.
Photo by Mimzy, available under Creative Commons CC0 1.0 license.
Photo by jievoyage, available under Creative Commons CC0 1.0 license.
Photo by Mark Bradshaw, available under Creative Commons BY 2.0 license.
Photo by Sam Churchill, available under Creative Commons BY 2.0 license.
Photo by 3844328, available under Creative Commons CC0 1.0 license.
New requirements -> new solutions
Zeebe in a nutshell
Support streaming & batching
Append only log / event sourcing
3 Nodes 30 Nodes
Distributed system with topics & partitions
P2 : F
P3 : L
P2 : F
P3 : F
P2 : L
P3 : F
- Topic with 3 partitions
and replication factor 3
- PX = Partition X
- L = Leader
- F = Follower
Replication uses the Raft protocol
The box said
so I installed
Status & Roadmap
• Tech preview (0.4.0)
• Working towards production-ready state
• Focus on core, not (yet) on completeness of features
• We love to get your feedback and discuss!
Architecture choices (examples)
*Isolation and autonomy can also
be achieved in this architecture
the monolith Microservices some hybrid*
Zeebe Uber Cadence Netflix
Client language or
Java, Go Go Java, REST AWS SDK, REST
Persistent storage Event log
on file system
Cassandra Netflix Dynomite
OSS, backed by
OSS project OSS project Cloud
Distribution Source, Binary Source Source -
Flow language BPMN, YAML, Java YAML, Go JSON JSON
Visibility BPMN None Proprietary Proprietary
**(for Biz and Dev)* (and mature)
Should I throw away my traditional workflow engine?