Slides from my talk at the Kafka Summit San Francisco 2018 about orchestration vs. choreography as well as track vs. manage event flows. Source code for live demos available on https://github.com/berndruecker/flowing-retail
5. The microservice community favours an
alternative approach: smart endpoints and
dumb pipes.
[… Microservices …] are choreographed using
simple RESTish protocols rather than complex
protocols such as WS-Choreography or BPEL or
orchestration by a central tool.
https://www.martinfowler.com/articles/microservices.html
10. The danger is that it's very easy to make
nicely decoupled systems with event
notification, without realizing that you're
losing sight of that larger-scale flow, and
thus set yourself up for trouble in future
years.
https://martinfowler.com/articles/201701-event-driven.html
11. The danger is that it's very easy to make
nicely decoupled systems with event
notification, without realizing that you're
losing sight of that larger-scale flow, and
thus set yourself up for trouble in future
years.
https://martinfowler.com/articles/201701-event-driven.html
12. The danger is that it's very easy to make
nicely decoupled systems with event
notification, without realizing that you're
losing sight of that larger-scale flow, and
thus set yourself up for trouble in future
years.
https://martinfowler.com/articles/201701-event-driven.html
15. What we wanted
Photo by Lijian Zhang, available under Creative Commons SA 2.0 License and Pedobear19 / CC BY-SA 4.0
16. Finding the right balance
16
Observe Microservice Paradigms
● Loose Coupling
● Autonomy
● Event Collaboration
Ensure Flow Manageability
• End-To-End Visibility
• Meet Business Process SLA
• Support Continuous Process
Improvement
17. Workflow automation | orchestration
is an essential building block
in microservice architectures
Of course I am opinioated – but I truly believe this!
18. Workflow automation | orchestration
is an essential building block
in microservice architectures
Of course I am opinioated – but I truly believe this!
Orchestration is not a central thing!
„It is not BPEL“
20. HQ Germany (Berlin) + Offices in US
bernd.ruecker@camunda.com
@berndruecker
Bernd Ruecker
Co-founder and
Developer Advocate of
Camunda
21.
22. Different levels of leveraging workflow automation
Manage the flowTrack the flow
Non-invasive, read-only
Additionally to choreography
Limited in power
Needs to be incorporated
Mixture of choreography and orchestration
Leverage full potential
23. A possible journey from pogo to beauty…
Manage the flowTrack the flow
Non-invasive, read-only
Additionally to choreography
Limited in power
Needs to be incorporated
Mixture of choreography and orchestration
Leverage full potential
25. Tracking + BI
Checkout Inventory
Payment Shipment
Kafka
Zeebe
Camunda
Optimize
Other reporting
/ BIO solutions
26. Tracking + BI
Checkout Inventory
Payment Shipment
Kafka
Workflow
Engine
Camunda
Optimize
Other reporting
/ BIO solutions
27. Tracking + BI
Checkout Inventory
Payment Shipment
Kafka
Zeebe
Camunda
Optimize
Other reporting
/ BIO solutions
This is totally non-invasive
But also limited in power
31. Why so shy?
Photo by LuidmilaKot, available under Creative Commons CC0 1.0 License.
32. A possible journey away from pogo…
Manage the flowTrack the flow
Non-invasive, read-only
Additionally to choreography
Limited in power
Needs to be incorporated
Mixture of choreography and orchestration
Leverage full potential
54. Workflow automation at scale!
low latency,
high-throughput
low frequency,
latency doesn‘t matter
What people think workflow
automation can do
What we currently teach
workflow automation
to be able to do
What workflow automation
can already do today
57. Recap
• In event-driven-systems it is easy to loose sight of the flow
• Visibility is essential to survive
• You need to balance orchestration and chorography
• Distributed systems need stateful orchestration
• Track, monitor or manage the flow – it might be a journey
• Workflow automation is an essential building block
• BPMN is very powerful and provides BizDevOps