Neue zeiten verlangen nach neuen Paradigmen - Bernd Rücker
•Download as PPTX, PDF•
0 likes•514 views
This document discusses microservices and distributed systems. It notes that microservices involve small, isolated components with clear responsibilities. It provides examples of how services like inventory, payment, and shipping could work together using messages and events. The document discusses challenges like asynchronous collaboration, distributed transactions, and handling things like timeouts and retries in a distributed environment. It also discusses approaches like orchestration and choreography for coordinating services and processes across microservice boundaries.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Neue zeiten verlangen nach neuen Paradigmen - Bernd Rücker
Similar to Neue zeiten verlangen nach neuen Paradigmen - Bernd Rücker (20)
More from camunda services GmbH
More from camunda services GmbH (20)
Recently uploaded
Recently uploaded (20)
Neue zeiten verlangen nach neuen Paradigmen - Bernd Rücker
- 1. Neue Zeiten verlangen nach neuen Paradigmen bernd.ruecker@camunda.com Co-founder and developer advocate
- 2. Neue Zeiten verlangen nach neuen Paradigmen …und nach englischen Folien…
- 3. Software is eating the world. Marc Andreessen, Entrepreneur & Investor „
- 5. Do you know Game Neverending?
- 7. to pivot | pivoted, pivoted | [Tech]
- 8. If you are not embarrassed by the first version of your product, you’ve launched too late. Reid Hoffman, Co-Founder LinkedIn (and others) „
- 9. Microservices: It is about speed and agility at scale • Small components with clear responsibilities • Isolation • Autonomy • Replaceability • Flexibility • Experimentation • Resilience • Individual scalability DevOps, polyglott, asynchronous, reactive, message- / event-driven
- 11. Example InventoryPayment ShippingCheckout Bus Order Placed Does not know recepient Does not know sender Event: Fact that happened in the past, Immutable fact, 0..n recepients Order Placed
- 12. It is not SOA InventoryPayment ShippingCheckout Bus Order Placed Does not know recepient Does not know sender Event: Fact that happened in the past, Immutable fact, 0..n recepients Order Placed Smart endpoints and dumb pipes
- 15. Service A Challenge: Asynchronous collaboration Send message to B Service B Wait for response Timeout handling Message correlation & deduplication State handling Parallelism & merging
- 16. Challenge: Distributed transactions 1. book hotel 2. book car 3. book flight 6. cancel hotel 5. cancel car 4. In case of failure trigger compensations book trip Service A Car ServiceHotel Service Flight Service ACID-Transactions only local in the service contexts Distributed transaction via Saga pattern using compensating activities
- 17. BPMN can help
- 18. BPMN can help
- 19. BPMN can help
- 20. Toolbox for distributed systems Handling of time & timeouts Retry Versioning Compensation & Saga Message correlation & deduplication Performance & scalability
- 21. The microservice community *Picture randomly taken from http://wareflo.com/2016/11/from-apis-to-microservices-workflow-orchestration-and-choreography-across-healthcare-organizations/. Not connected to statements on slide. Orchestration… …introduces single point of failure… …leads to god services… …leads to tight coupling… „
- 22. Example InventoryPayment ShippingCheckout Bus Order Placed Decentral data management Event: Fact that happened in the past, Immutable fact, 0..n recepients Customer status changed
- 23. End-to-end processes using eventflows? InventoryPayment ShippingShop Order placed Payment received Goods fetched Goods shipped
- 24. Commanding is important InventoryPaymentOrder ShippingShop Bus Order Placed Event: Fact that happened in the past, Immutable fact, 0..n recepients Order Placed Command: Intend, 1 recipient. Coupling the other way round Retrieve Payment Fetch Goods Ship Goods
- 25. The case for orchestration
- 26. The end-to-end order process?
- 27. End-to-end processes cross microservice boundaries Order Inventory Payment
- 28. For execution: respect boundaries and distribute ownership
- 29. Payment Processes are “implementation detail” of services Order Distributed orchestration
- 30. And that‘s good?
- 31. End-to-end processes as 1st class citizen InventoryPaymentOrder ShippingCheckout Core Capabilities Support Capabilities Business Capabilities
- 32. Finally!
- 33. Order Order Order Order Architecture Order Engine A Payment Engine B Monitoring Human Task Management Coarse grained central monitoring Fine grained monitoring & operations (per context) DevOps Tec Ops Biz Ops Central
Editor's Notes
- https://www.flickr.com/photos/techcrunch/29035377473
- On the one hand technical changes of infrastructure Systems become more connected, complex and distributed than ever before.
- But on the other hand a much bigger force
- „umschwenken“ / pivotieren MVP Iteratives Vorgehen, Step by Step
- http://www.istockphoto.com/de/foto/wicked-wind-grand-haven-lighthouse-michigan-usa-gm135811641-18609389
- http://www.istockphoto.com/de/foto/wicked-wind-grand-haven-lighthouse-michigan-usa-gm135811641-18609389
- Problems: re-ordering of services? New requirements & 3-legged-race .. Missing: Point where to change things No visibility of current state (probably done vaguely with Tracing)
- Vielleicht in der Design-Phase mal aufmalen
- Das kann nen fachlichen Wert haben! Wir sollten es aber so vielleicht nicht ausführen. Aber zum verstehen ist es cool. Aber in der Realisierung!
- A process should not be bound to organziational structure.
- Separation of concerns Focus of single services Divide and conquer
- A process should not be bound to organziational structure.
- There is some homework to do here – but we have it on the radar Hier sollten wir als BPM aufholen und uns Gedanken machen Da gibt es viel zu liefern & zu lernen – da wird viel passieren Ich hab ein einfaches Beispiel ne kollab mit bpmn.io aus distributed orchestration zusammen anzuzeigen. Das geht evtl. einfach. Im Betrieb & Verbesserung also wieder zusammen bringen – da wird es spannend Demo verfügbar
- Microservices most prbably will happen Executable BPMN processes help to implement services within distributed systems End-to-end processes are 1st class citizens, but composed out of pieces fitting the (microservice) boundaries
- https://c1.staticflickr.com/7/6234/6292833167_f61171f078_b.jpg
- https://www.weforum.org/agenda/2016/01/the-fourth-industrial-revolution-what-it-means-and-how-to-respond/
- This is not black / white. There is no all-in decision necessary. …
- Aber events sind großartig. Nicht nur technisch scale auch natürlicher. Fachlich einfacher Bpmn potentiell vor allem Ausführungssprache! BizDevOps. Do not overrate roundtrip.
- A lot of systems will be event- but also domain-driven microservices in future End-to-end processes must respect responsibility and ownership and be sliced into appropriate pieces. Use distributed orchestration instead of monolithic BPM BPMN can keep on serving as great executable flow language – yeah! The challenges for services collaboration (the „between the services“) will increase, workflow technology can be a great help here.
- http://www.istockphoto.com/de/foto/wicked-wind-grand-haven-lighthouse-michigan-usa-gm135811641-18609389
- https://www.thoughtworks.com/insights/blog/building-reliable-digital-operations Think about a new function that just does XXX when event YYY occurs -> go for it!
- This is not black / white. There is no all-in decision necessary. …
- http://www.istockphoto.com/de/foto/woman-making-payment-through-nfc-gm600372530-103229019 http://www.istockphoto.com/de/foto/unternehmer-er%C3%B6ffnung-einem-gepolsterten-umschlag-gm535503768-94969443
- But it seems not to really improve – developers are still afraid of „BPM“ Time to introduce a new word for it!
- Developer friendly even morre consequent as in the past: Ployglot, XAML & JSON, focus on concrete developer problems at hand, … Composable: not only Java with e.g. Spring Boot, but also within Go and other
- nicht nur das tecki Lager lehnt es ab Scheinbar müssen wir was besser machen / können was lernen)
- http://www.istockphoto.com/de/foto/zwei-m%C3%A4nner-die-faust-gem%C3%A4ldename-modernen-h%C3%A4nde-sch%C3%BCtteln-gm146799551-11630992
- Does not fit anywhere.
- Like e.g. Bridge18: Will only be there for some time until self-driving trucks have arrived – which will again change everything!
- Do you remeber that one release a quarter done in insurance industries? The times where they bought BPM to be able to deploy faster