Blowing up the Monolith: Practical Advice on Microservices
•
1 gostou•228 visualizações
Many companies are transitioning to microservices but what factors influence whether or not to “blow up” your monolith? The advantages of moving to a microservices architecture include increased performance, deployability and scalability, but these advantages come at the cost of increased complexity. This presentation will cover the architectural considerations involved in transitioning from a monolithic to a microservices or service-oriented architecture. Take a technical look into the factors to consider during a transition including how to define boundaries between microservices, interservice communication patterns and testing. Learn strategies for transitioning such as the “ice cream scoop,” “lego” and “nuclear” options, routing and versioning strategies, and how to handle libraries and security to maximize service independence.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Blowing up the Monolith: Practical Advice on Microservices
Semelhante a Blowing up the Monolith: Practical Advice on Microservices (20)
Mais de Nordic APIs
Mais de Nordic APIs (20)
Último
Último (20)
Blowing up the Monolith: Practical Advice on Microservices
- 1. Nordic API
- 4. konghq.com Monolith Services Microservices/ Service Mesh Journey to a modern Enterprise Emerging PatternsServerless/FaaS + N-S N-S N-S N-S E-W N-S
- 5. konghq.com What does it mean?
- 6. konghq.com Refactoring a monolith is an activity that unlocks team productivity and business scalability
- 7. konghq.com Refactoring a monolith is an activity that unlocks team productivity and business scalability
- 8. konghq.com Should we do it?
- 9. konghq.com
- 11. konghq.com
- 13. konghq.com Ice Cream Scoop Lego Strategy Nuclear Strategy
- 14. konghq.com Ice Cream Scoop Lego Strategy Nuclear Strategy
- 15. konghq.com Class Class Class Class Class Class Class Class Class ClassClassClass Database Object-Oriented Monolith Lots of function calls across different objects
- 16. konghq.com Users Search Orders Inventory Invoices Billing Items Reviews Payouts PointsOffersPartners Database Hypothetical Marketplace Like Amazon.com
- 17. konghq.com Users Search Orders Inventory Invoices Billing Items Reviews Payouts PointsOffersPartners Database Team 1 Team 2 Team 3
- 19. konghq.com Users Orders Invoices Billing PayoutsPoints OffersPartners Database Team 1 Team 2 Team 3 Search Inventory Items Reviews Database
- 20. konghq.com Users Orders Invoices Billing PayoutsPoints OffersPartners Database Team 1 Team 2 Team 3 Search Inventory Items Reviews Database Database
- 21. konghq.com Clear understanding of what the Monolith does and does not Understanding of clients that are consuming the monolith Tests, Tests, Tests.
- 23. konghq.com Frontend Load Balancer N-S Traffic N-S Traffic Users Search Orders Inventory Invoices Billing Items Reviews Payouts PointsOffersPartners Monolith
- 24. konghq.com Frontend API Gateway N-S Traffic N-S Traffic Users Search Orders Inventory Invoices Billing Items Reviews Payouts PointsOffersPartners Monolith API Gateways are also load balancers
- 25. konghq.com Frontend API Gateway Users SearchOrders InventoryInvoices Billing Items Reviews PayoutsPoints OffersPartners E-W Traffic Routing
- 26. konghq.com Frontend API Gateway Users SearchOrders InventoryInvoices Billing Items Reviews PayoutsPoints OffersPartners E-W Traffic Canary Release (ie, 10% traffic) Search Inventory Items Reviews v1.0 v1.1
- 29. konghq.com Service Service Service Service Service Service Service Service Service ServiceServiceService Database Database Database Database Ideal World
- 32. konghq.com In monoliths we have objects , interfaces and function calls. In microservices we have services , interfaces, and network calls.
- 33. konghq.com Service Service Service Service Service Service Service Service Service ServiceServiceService Database Database Database Database Microservices Lots of network calls across different services Network
- 34. konghq.com 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
- 35. konghq.com 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
- 36. konghq.com local ServiceService Success Rate 100% Network Latency 0ms Success Rate 100% Network Latency 0ms Proxy Proxy
- 38. konghq.com 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
- 39. konghq.com 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) DP External Clients
- 40. CNS Central Nervous System PNS Peripheral Nervous System N E R V O U S S Y S T E M
- 41. N E R V O U S S Y S T E M Control Planes For configuration and metrics Open Source Data Planes Lightweight and Decentralized Data Planes
- 42. N E R V O U S S Y S T E M O F T H E C L O U D MONOLITH SERVICES MESH SERVERLESS
- 43. WW Kick-off 2019 Business Pragmatic Adopting
- 44. konghq.com Download Kong at konghq.com