9. Important: Avoid the 7 sins!
https://blog.bernd-ruecker.com/the-7-sins-of-workflow-b3641736bf5c
10. The 7 sins of workflow
Homegrown
engine
No engine Wrong engine
4
6
5
7
3
11. Think about subsequent requirements
Monitoring &
Operations
Visibility
Versioning
Time &
Timeouts
Domain Logic
Operate at
scale
12. The 7 sins of workflow
Zero-code suites
Homegrown
engine
No engine Wrong engine
4
6
5
7
13. Avoid zero-code suites!
Death by properties panel
Low-code is great!
(You can get rid
of your developers!)
Complex, proprietary, heavyweight, central, developer adverse, …
14. Zero code meets developers
We have
some problems
It is horrible.
I hate BPM!
15.
16. Why is this so important?
Some advice to
convince your boss!
17. Software is
eating the
world.
Marc Andreessen,
Entrepreneur &
Investor
2011 in „The Wall
Street Journal“
„
Photo by techcrunch, available under Creative Commons BY 2.0 license.
18. “Goldman Sachs is a Tech Company”
18
https://media.thinknum.com/articles/the-bank-jobs-which-big-financial-firms-are-betting-heavy-on-tech/
19.
20. From the Microsoft Press Release
20
https://news.microsoft.com/2018/06/04/microsoft-to-acquire-github-for-7-5-billion/
Today, every company is becoming a software
company and developers are at the center of digital
transformation; they drive business processes and
functions across organizations from customer
service and HR to marketing and IT. And the choices
these developers make will increasingly determine
value creation and growth across every industry.
21. Camunda Open source platform for workflow and
decision automation.
Developer friendly!
> 75 people
HQ Berlin + Offices US
0
20
40
60
80
100
120
140
160
180
200
2014 2015 2016 2017 2018
27. <= milliseconds seconds minutes, weeks, …
Business
IT
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
28. <= milliseconds seconds minutes, weeks, …
Business
IT
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
Long running =
sit and wait
29. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
30. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
31. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
Distributed
Transactions
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
35. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
Distributed
Transactions
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
36. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
Distributed
Transactions
Orchestration
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
39. Peer-to-peer communication (e.g. via events)
Checkout
Payment
Inventory
Shipment
Order
placed
Payment
received
Goods
shipped
Goods
fetched
40. Peer-to-peer communication (e.g. via events)
Checkout
Payment
Inventory
Shipment
Order
placed
Payment
received
Goods
shipped
Goods
fetched
41. 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
42. 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
43. 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
53. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
Distributed
Transactions
Orchestration
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
54. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
Distributed
Transactions
Orchestration
Communication in
distributed systems
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
58. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
Distributed
Transactions
Orchestration
Communication in
distributed systems
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
59. <= milliseconds seconds minutes, weeks, …
Business
IT
Business processes
automation
Distributed
Transactions
Decision
Automation
Orchestration
Communication in
distributed systems
long runningalways short running short running, but
potentially long running
Use cases for workflow automation
67. Who has no problems
operating a message bus?
Dead messages | No context | Inaccesible payload | Hard to redeliver |
Home-grown message hospitals | …
71. 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
73. Biz Dev
Leverage
state machine &
workflow engine
Living
documentation
Visibility in
testing
improve
communication
improve
communication
Ops
74. Biz Dev
Leverage
state machine &
workflow engine
Living
documentation
Visibility in
testing
Understand and discuss
business processes
Evaluate optimizations
in-sync with
implementation
improve
communication
improve
communication
Ops
76. Biz Dev
Leverage
state machine &
workflow engine
Living
documentation
Visibility in
testing
Understand and discuss
business processes
Evaluate optimizations
in-sync with
implementation
improve
communication
improve
communication
Ops
77. Biz Dev
Leverage
state machine &
workflow engine
Living
documentation
Visibility in
testing
Operate with visibility
and context
Understand and discuss
business processes
Evaluate optimizations
in-sync with
implementation
improve
communication
improve
communication
Ops