Downloaded 12 times
![38
“Organizations which design systems [...]
produce designs which are copies of the
communication structures of these organizations.”
M. Conway
Organisational Considerations – Conway’s Law](https://image.slidesharecdn.com/microservice-communication-191205120628/75/Communication-in-a-Microservice-Architecture-38-2048.jpg)
Uploaded byPer Bernhardt
Communication in a Microservice Architecture
The document discusses communication strategies in microservice architecture, focusing on synchronous versus asynchronous integration, distributed transactions, and service routing. It outlines key concepts including the fallacies of distributed computing, orchestration vs. choreography, and eventual consistency challenges. Additionally, it highlights organizational considerations based on communication structures as well as best practices for implementing microservices.
More Related Content
Similar to Communication in a Microservice Architecture
Communication in a Microservice Architecture
- 1. Communication in a MicroserviceArchitecture Per Bernhardt, Staff Software Engineer December 4th 2019
- 2.
- 3.
- 4. 4 Basics Synchronous vs. AsynchronousIntegration Distributed Transactions vs. Eventual Consistency Service Routing Organisational Considerations Q & A Agenda
- 5.
- 6. 6 Basics – Leavingthe Process User Content Search Sales Suggestions Images User Content Search Sales Suggestions Images
- 7. 7 Basics – Fallaciesof distributed computing The network is reliable Latency is zero Bandwidth is infinite The network is secure Topology doesn't change There is one administrator Transport cost is zero The network is homogeneous
- 8. 8 Basics – Typesof communication Synchronous protocol Sender Receiver Request Response Asynchronous protocol Sender Receiver Request
- 9. 9 Basics – Typesof communication Single Receiver Multiple Receiver Sender Receiver Sender Receiver Receiver Receiver
- 10. 10 Basics – Typesof communication Orchestration Choreography Customer Service Loyality Service Post Service Email Service “Customer Created” Customer Service Loyality Service Post Service Email Service “Create Points Balance!” “Send Welcome Email” “Send Welcome Pack”
- 11. 11 Basics – RecommendedReadings https://docs.microsoft.com/de- de/dotnet/architecture/microservices/architect- microservice-container-applications/
- 12.
- 13. 13 Synchronous vs. AsynchronousIntegration User Content Sales … Suggestions Images Frontend API New Frontend Synchronous
- 14. 14 Synchronous vs. AsynchronousIntegration User Content Sales … Suggestions Images Frontend API New Frontend Content Images Suggestions Sales Synchronous Asynchronous
- 15. 15 Synchronous vs. AsynchronousIntegration User Content Sales … Suggestions Images Frontend API New Frontend Content Images Suggestions Sales Asynchronous Content ImagesContentImages
- 16. 16 Synchronous vs. AsynchronousIntegration “The one-hop rule: A service should not call other services to respond to a request.” https://messente.com/blog/most-recent/5-mistakes-transition-to-microservices
- 17. 17 Synchronous vs. AsynchronousIntegration “Simply put, without decoupling the data, the architecture is not microservices.” https://martinfowler.com/articles/break-monolith-into-microservices.html
- 18. 18 Synchronous vs. AsynchronousIntegration “So what about authentication??” Some random developer
- 19.
- 20. 20 Distributed Transactions vs.Eventual Consistency - Transactions are technically hard…
- 21. 21 Distributed Transactions vs.Eventual Consistency – The Two Phase Commit (2PC)
- 22. 22 Distributed Transactions vs.Eventual Consistency – Eventual Consistency is conceptually hard…
- 23. 23 Distributed Transactions vs.Eventual Consistency – Eventual Consistency Content Service Search Service Updates content Searches content Eventually consistent
- 24. 24 • Search Servicehas a daily cronjob • Fetches all content via REST API • Search Index is eventually consistent “the next day” Synchronous protocol + Orchestration Distributed Transactions vs. Eventual Consistency – Eventual Consistency done “simple”
- 25. 25 Distributed Transactions vs.Eventual Consistency – Eventual Consistency done “hard” • Content Service pushes update events to message queue • Search Service subscribed to content update events • Search Index is eventually consistent “every few seconds” Asynchronous protocol + Choreography
- 26. 26 Distributed Transactions vs.Eventual Consistency – Eventual Consistency done “hard” • Guaranteed Delivery • Idempotent Receiver • …
- 27.
- 28. 28 Service Routing –Just a mess
- 29. 29 Service Routing –Just a mess Service A Service B http://10.0.1.78
- 30. 30 Service Routing –Container orchestration Service A Service B http://10.0.1.78 kube-dns 10.0.1.78service-b ingress cluster https://service-b.leanix.net
- 31. 31 Service Routing –Container orchestration • Local Service Routing • Ingress Routing • Ingress HTTPs Encryption
- 32. 32 Service Routing –Router Model Service A Service B cluster-westeurope cluster-eastus Router https://service-b.leanix.net
- 33. 33 Service Routing –Router Model • Global Service Routing • Rate Limiting • Caching • Generic Error Pages
- 34. 34 Service Routing –Service Mesh Service A Service B cluster-westeurope cluster-eastus proxy proxy Gateway Control Plane
- 35. 35 Service Routing –Service Mesh • Ingress & Egress Encryption • Traffic Optimisation • Metrics • Tracing • Circuit Breaker
- 36.
- 37. 37 “Speech is silver,silence is golden.” Don Quijote Organisational Considerations – Rule of Thumb
- 38. 38 “Organizations which designsystems [...] produce designs which are copies of the communication structures of these organizations.” M. Conway Organisational Considerations – Conway’s Law
- 39.
- 40.
- 41.