Speaker: Bernd Rücker, Mitgründer und Developer's Advocate Microservice-Architekturen finden zunehmend Verbreitung. Doch viele Fragen bleiben unbeantwortet: Wie sorge ich dafür, dass meine Geschäftsprozesse über die verteilten, unabhängigen Services hinweg zuverlässig ausgeführt werden? Wie organisiere ich den technischen Betrieb, der eine zentrale Anlaufstelle für die Fehlererkennung und -behebung benötigt? Und wie kann ich diese Probleme lösen, ohne das Paradigma der losen Kopplung von Microservices zu verletzen? Camunda-Mitgründer Bernd Rücker wird aufzeigen, wie sich Microservice-Architekturen mit Camunda erfolgreich aufbauen und betreiben lassen.

1. Microservices with Camunda
bernd.ruecker@camunda.com | @berndruecker
Co-Founder & Developer Advocate

2. What I do not need to talk about today:
AirBnb, Uber, Ebay, Deliveroo, …
Lemonde, PayPal, N26, …
Tesla, …
Amazon, Google, Apple, …

3. 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.

4. to pivot | pivoted, pivoted | [Tech]
50 percent of IoT solutions (typically a
product combined with a service) will
originate in startups that are less
than three years old.
Gartner
„

5. If you are not
embarrassed
by the first
version of your
product, you’ve
launched too
late.
Reid Hoffman,
Co-Founder LinkedIn
(and others)
„
Photo by joi, available under
Creative Commons BY 2.0 license

6. Photo by born1945, available under Creative Commons BY 2.0 license.

7. Basic idea of dedicated, autonomous (micro-) services
Checkout
Payment
Inventory
Shipment
Dedicated Application Process
Dedicated Persistence Backend
Dedicated Ownership & Dev Team

8. So that‘s what I do not need to talk about
today…
…I want to talk about what this means for
workflow automation and BPM.

9. Workflow automation in „the serverless age“
# More use cases
# Different way to think about BPM

10. The complexity moves to the collaboration of services
Checkout
Payment
Inventory
Shipment
A lot of services

11. Distributed systems

12. Checkout
Payment
Inventory
Shipment
Typical solution approaches:
- Circuit breaker
- Bulkheads
- Service Mesh
- …
 Fail fast

14. Better! This can take
days to complete!
HTTP: 202 - ACCEPTED
HTTP: 200 - OK

15. Checkout
Payment
Inventory
Shipment
2007

16. BPMN

17. Persistent state handling for long running behavior

18. Workflow automation in „the serverless age“
# More use cases
# Different way to think about BPM

19. Not only but also at scale

20. BPM architecture - the traditional view
BPM This is an Anti-Pattern in
microservice architectures!

21. Workflows live inside service boundaries
In DDD:
Bounded
Contexts

22. Workflows live inside service boundaries
The
busines process as
first class citizen

23. Finally!

24. Example
InventoryPaymentOrder ShippingCheckout Monitor
https://github.com/flowing/flowing-retail/
Human
Tasks
H2 H2

25. Good workflow technology
is lightweight and flexible*
and thus can also run decentralized
*think of it as a library

26. Reality Check

28. Zalando
Sales-Order and
Order-Fulfillment
via Camunda
for every order worldwide
Orders Q2-2017: 22,2 Mio.
Sales 2016: 3,6 Mrd. EUR
Growth 2016: 23%

30. Thank you!

31. Contact:
bernd.ruecker@camunda.com
@berndruecker
Slides:
https://bernd-ruecker.com
Blog:
https://blog.bernd-ruecker.com
Code online:
https://github.com/flowing
https://www.infoq.com/articles/
events-workflow-automation With thoughts from http://flowing.io
@berndruecker | @martinschimak