39. Resilience
[…] the workflow that defines in which order
and how (location, input parameters,
timeouts, etc.) activities are executed is
guaranteed to continue execution under
various failure conditions.
39
46. Visibility
“[…]
as the number of
microservices grows
and the complexity of
the processes increases,
getting visibility into
these distributed
workflows becomes
difficult without a
central orchestrator.”
46
51. Workflow
- A unified model for Asynchronous and Event-Driven Processing
- Provides Resilient Orchestrations
- Provides Visibility and Control
51
52.
53. • 160 customers in >20 countries
• > 85% of customers use Camunda for core business processes
• Self funded & profitable. Revenue in growth 2016: 82%
• 70 Employees
Camunda
AT&T
53
55. Meet Zeebe
“Zeebe” a new Microservice Orchestration & Workflow Engine.
Zeebe is Open Source and available at
• https://zeebe.io (Website)
• https://github.com/zeebe-io (Github)
55
56. Zeebe’s Mission
Zeebe is pushing the boundaries of what is possible with workflow.
• Extremely high throughput: more than 100x better than trad. engines on a single node
• Horizontally scalable
• Highly available, resilient and fault tolerant
• Completely asynchronous and reactive
56
63. Persistence
Generate Event Stream
Internally Zeebe works as an Event Sourcing System.
As Zeebe advances through a Workflow Instance, it generates a stream of events.
This event stream is both history but also “drives the execution forward”.
63
65. Thank you.
(Come work on Zeebe.io: If you want to help us make a difference pushing the
boundaries of what is possible with workflow, Camunda is hiring)