Camunda Con Live 2020 Keynote - Microservice Orchestration and Integration

Slides from my talk at Camunda Con Live on 24th of April 2020 about orchestrating and integrating microservices and the connection of choreography, observability and workflow automation

1. 1
Microservices Orchestration
and Integration
using Workflow Automation
Bernd Ruecker
Co-Founder and Chief Technologist

2. Service
A
Microservices
@berndruecker
Monolith
Service
B
Service
C
C
B
A
D

3. Change istheonlyconstant
„
Wedon‘tknowwhatwewill needtomorrow.
But wedo knowthatwewill needsomething.
Wehavetobeabletomovequickly!
CIO ofan insurancecompanyin 2019

4. Service
A
AutonomousMicroservices
@berndruecker
Service
B
Service
C

5. The eraofAPIs
API
API
API
API
API
API
API
API
@berndruecker

6. The eraofAPIs
API
API
API
API
API
API
API
External Services
Standard Software
API
Functions
@berndruecker

7. Connectingthedots…
API
API
API
API
API
API
API
Microservices
External Services
Standard Software
API
Functions
@berndruecker

8. Example
@berndruecker

9. Example
Payment
Seat
Reservation
Booking
Ticket
Generation

10. Example
@berndruecker
sync

11. Weaknesses
Payment
Seat
Reservation
Booking
Ticket
Generation
REST

12. Weaknesses: Latencycreep
Payment
Seat
Reservation
Booking
Ticket
Generation
REST
300 ms
1150 + x ms
600 ms
250 ms

13. Weaknesses: Availabiliyerosion
Payment
Seat
Reservation
Booking
Ticket
Generation
REST
99 % uptime
99 % uptime
99 % uptime
96 % uptime

14. Example
@berndruecker

15. And itisevenhardtoimplement
Payment
Seat
Reservation
Booking
Ticket
Generation
REST

16. And itisevenhardtoimplement
Payment
Seat
Reservation
Booking
Ticket
Generation
REST

17. Workflow automationcanhelp
Payment
Seat
Reservation
Booking
Ticket
Generation
REST
Workflow Automation:
Isstateful
Canwait
Canretry
Canescalate
Cancompensate

18. Typicalpattern
Payment
Seat
Reservation
Booking
Ticket
Generation
REST
Simulatesynchronictybywaiting
(callbackorpolling)

19. Can yourcompany
leverageyour
hipster architecture?
Shutterstock
Youneedto
change business
processesand
customer
experience!

20. @berndruecker
happy
case
failure
case
Redesignyourbusinessprocessaccordingly!
Orsomeinterface
topollfor status
Syncin happy case
Asyncresponse

21. @berndruecker
Redesignyourbusinessprocessaccordingly!

22. @berndruecker
https://www.reactivemanifesto.org/

23. Yeah!
Let‘sgoreactive.

24. Phil Calcadoat QConNYC 2019

25. API
API
API
API
API
API
API
Microservices
External Services
Standard Software
„Whatthehell just happened?“
@berndruecker

26. Example:
orderfulfillmentvia
dashbutton
Photo by0xF2, availableunderCreative Commons BY-ND 2.0
license. https://www.flickr.com/photos/0xf2/29873149904/
@berndruecker

27. Threesteps…
@berndruecker

28. (Micro-)services
Checkout
Payment
Inventory
Shipment
@berndruecker

29. Order
Placed
Payment
Received
Goods
Fetched
Notification
Checkout
Payment
Inventory
Shipment
Event-drivenarchitecture
@berndruecker

30. Peer-to-peereventchains
Checkout
Payment
Inventory
Shipment
Order
placed
Payment
received
Goods
shipped
Goods
fetched
@berndruecker

31. Peer-to-peereventchains
Checkout
Payment
Inventory
Shipment
Order
placed
Payment
received
Goods
shipped
Goods
fetched
@berndruecker

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

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

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

35. ProcessEvents Monitoring
Camunda
Optimize
Order
placed
Payment
received
Goods
fetched
Goods
shipped
@berndruecker
Order
placed
Payment
received
Goods
fetched
Goods
shipped

36. Demo

37. Peer-to-peereventchains
Checkout
Payment
Inventory
Shipment
Order
placed
Payment
received
Goods
shipped
Goods
fetched
@berndruecker

39. Peer-to-peereventchains
Checkout
Payment
Inventory
Shipment
Order
placed
Payment
received
Goods
shipped
Goods
fetched
Fetchthegoods
beforethe
payment
@berndruecker

40. Peer-to-peereventchains
Checkout
Payment
Inventory
Shipment
Goods
fetched
Order
placed
Payment
received
Goods
shipped
@berndruecker

41. Whatwewanted
Photo by LijianZhang, availableunderCreative Commons SA 2.0 Licenseand P..19/ CC BY-SA 4.0
@berndruecker

42. Order
Extracttheend-to-end responsibility
Checkout
Payment
Inventory
ShipmentPayment
received
Order
placed
Retrieve
payment
@berndruecker

43. Order
Events & Commands
Checkout
Payment
Inventory
ShipmentPayment
received
Order
placed
Retrieve
payment
@berndruecker
Event
Command
Fact,
happened in the past,
immutable
Intend,
Want s.th. to happen

44. Order
Itisnot abouttheprotocol!
Checkout
Payment
Inventory
Shipment
Order
placed
Retrieve
payment
Itcanstill bemessaging!
@berndruecker

45. Order
Itisaboutwheretodecideaboutthecoupling!
Checkout
Payment
Inventory
Shipment
Order
placed
Retrieve
payment
Order decides
. tolisten totheevent
. toissuethecommand
@berndruecker

46. Order
Checkout
Payment
Inventory
Shipment

47. Demo

48. One of the largest online fashion retailers
in the world (> 14.000 employees) does
everyorder fulfillment worldwide
withCamunda & Kafka
@berndruecker

49. Workflows live insideserviceboundaries
@berndruecker

50. NoBPM(N) monoliths
https://blog.bernd-ruecker.com/avoiding-the-bpm-monolith-when-using-bounded-contexts-d86be6308d8
@berndruecker

51. YourIT architecture
Choreography
Orchestration
@berndruecker
Yourservices
orapplications

52. Monolith Chaos
Choreography
Orchestration
@berndruecker
ProcessMonitoring
Yourservices
orapplications

53. YourIT architecture
ProcessMonitoring
Monolith Chaos
Choreography
Orchestration
Yourservices
orapplications
Balance choreographyand orchestration
@berndruecker

54. Summary
•Business agilityisessential tosurvive, thisisthecase
for microservices
•Collaborationofservicesisthenewchallenge
•Balance orchestrationandchoreography
•Fromchoreographytoorchestrationcanbea journey
•Workflow automationisa essential buildingblock

55. Thankyou!
@berndruecker