APIdays Paris 2019 - Adopting Service Mesh by Marco Palladino , Kong
•
0 likes•43 views
This document discusses refactoring a monolithic application into microservices. It describes some benefits of using a service mesh pattern to implement microservices, including improving network performance by adding proxies to each service. The service mesh allows services to communicate asynchronously through an event-driven messaging system like Kafka. This architecture provides benefits like resiliency, observability, and the ability to develop services independently in different programming languages.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to APIdays Paris 2019 - Adopting Service Mesh by Marco Palladino , Kong
Similar to APIdays Paris 2019 - Adopting Service Mesh by Marco Palladino , Kong (20)
More from apidays
More from apidays (20)
Recently uploaded
Recently uploaded (20)
APIdays Paris 2019 - Adopting Service Mesh by Marco Palladino , Kong
- 1. APIdays.io
- 14. kuma.io
- 15. Refactoring a monolith is an activity that unlocks team productivity and business scalability
- 16. Refactoring a monolith is an activity that unlocks team productivity and business scalability
- 17. Should we do it?
- 18. O(1) to O(n)
- 20. Let’s do it!
- 21. Ice Cream Scoop Lego Strategy Nuclear Strategy
- 22. Ice Cream Scoop Lego Strategy Nuclear Strategy
- 23. Class Class Class Class Class Class Class Class Class ClassClassClass Database Object-Oriented Monolith Lots of function calls across different objects
- 24. Users Search Orders Inventory Invoices Billing Items Reviews Payouts PointsOffersPartners Database Hypothetical Marketplace Like Amazon.com
- 25. Users Search Orders Inventory Invoices Billing Items Reviews Payouts PointsOffersPartners Database Team 1 Team 2 Team 3
- 27. Users Orders Invoices Billing PayoutsPoints OffersPartners Database Team 1 Team 2 Team 3 Search Inventory Items Reviews Database
- 28. Users Orders Invoices Billing PayoutsPoints OffersPartners Database Team 1 Team 2 Team 3 Search Inventory Items Reviews Database Database
- 29. Service Service Service Service Service Service Service Service Service ServiceServiceService Database Database Database Database Ideal World
- 31. In monoliths we have objects , interfaces and function calls. In microservices we have services , interfaces, and network calls.
- 32. Service Service Service Service Service Service Service Service Service ServiceServiceService Database Database Database Database Microservices Lots of network calls across different services Network
- 33. Service Service Service Service Service Service Service Service Service ServiceServiceService Database Database Database Database Microservices Lots of network calls across different services Typical network problems: latency, security, routing, error handling, observability
- 34. Latency Service Service Service 1ms 3ms 1ms2ms Total network latency: 7ms
- 37. Error Handling / Resiliency Service Service Service Service
- 38. Observability Service Service Service Service Collector Service Service Service Service Service Service Service Service
- 40. Service Service Service Service Service Service Service Service Service ServiceServiceService Database Database Database Database Service Mesh Lots of network calls across different services through a decentralized proxy D P D P D P D P D P D P D P D P D P D P D P D P D P D P D P D P
- 41. local ServiceService Success Rate 100% Network Latency 0ms Success Rate 100% Network Latency 0ms Proxy Proxy
- 43. Service Service Service Service Service Service Service Service Service ServiceServiceService Database Database Database Database D P D P D P D P D P D P D P D P D P D P D P D P Control Plane (CP) Push dynamic configuration and act as TLS CA Collect metrics from sidecars D P D P D P D P
- 44. Service Service API GW Service Service Service Service Service Service ServiceServiceService Database Database Database Database D P D P D P D P D P D P D P D P D P D P D P D P Control Plane (CP) Other Teams / Products / Partners D P D P D P D P
- 45. Go Java API GW Python Java Go Ruby Java .Net JavaRuby.Net Database Database Database Database D P D P D P D P D P D P D P D P D P D P D P D P Control Plane (CP) Other Teams / Products / Partners D P D P D P D P
- 46. Microservices and clients directly consume and invoke other microservices. Service-To-Service (Synchronous) Event Based (Asynchronous) Microservices and clients push event into an event collector that’s being consumed by other microservices. Ideal for clients that require an immediate response or need to aggregate multiple services together. Ideal for microservice-to-microservice communication for changing state without requiring an immediate response. Done via HTTP, TCP/UDP, gRPC,etc. Done via Kafka, RabbitMQ, AWS SQS, etc. Example: Making a request to retrieve an immediate response of some sort (ie, retrieve list of users). Example: Making a request that doesn’t require an immediate response (ie, “orderCreated” event that triggers an invoice creation by another microservice).
- 47. Service Service API GW Kafka Service Service Service Service ServiceServiceService Database Database Database Database D P D P D P D P D P DP D P D P D P D P D P Control Plane (CP) Other Teams / Products / Partners D P D P D P D P
- 48. WW Kick-off 2019 A New Service Mesh Extended
- 49. WW Kick-off 2019 Implement Service Mesh at kuma.io