Slides from a joined meetup of Confluent/Kafka and Camunda/Zeebe in October 2019.
Code is here: https://github.com/berndruecker/flowing-retail/tree/master/kafka
10. Temporal decoupling with events and read models
Checkout
Payment
Inventory
Shipment
Good
Stored
Read
Model
Good
Fetched
The button blinks if we can
ship within 24 hours
*Events are facts about what happened (in the past)
@berndruecker
14. 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
@berndruecker
15. 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
@berndruecker
16. 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
@berndruecker
32. Order
It is about where to decide about the coupling!
Checkout
Payment
Inventory
Shipment
Order
placed
Retrieve
payment
Order decides
. to listen to the event
. to issue the command
@berndruecker
48. 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
• Workflow automation is an essential building block
• BPMN is very powerful and provides BizDevOps
• Zeebe rocks :-)
@berndruecker