The Next Generation of Microservices
1 like1,363 views
The document discusses the evolution of microservices architectures over time as techniques for handling issues like failures and timeouts were developed. It describes how early approaches involved adding timeouts and circuit breakers to code. Later, approaches involved sharing state between services and client-side service discovery. Today, sidecars and service meshes have moved reliability patterns lower in the stack, standardizing protocols and allowing services to abstract away operational concerns. However, meshes also introduce new tradeoffs around portability and development cycles.
The Next Generation of Microservices
- 1. The Next Genera,on of Microservices Phil Calçado h9p://philcalcado.com @pcalcado
- 3. highly distributed applica1on architecture We can think of microservices as
- 4. Highly distributed applica,on architectures are just a flavor of distributed compu1ng
- 5. Technical Challenges Organiza,on Challenges Introducing distribu,on into your architecture brings up new
- 6. Introducing distribu,on into your architecture brings up new
- 8. The example we will work with today: Recovering from temporary failure
- 11. "I know, let’s use microservices”
- 12. Timeouts Your code looks like this now Biz Logic Timeouts
- 13. server client
- 14. Timeouts Your code looks like this now Biz Logic Timeouts RPC code
- 17. 🔥 wait ☺ 😰 🔥 🔥 wait ☺ 😰 🔥 ☺ ☺ ☺ ☺ ☺ ☺ ☺ ☺
- 18. "I know, let’s implement circuit breakers and ,meouts”
- 19. Circuit breakers Timeouts Your code looks like this now Biz Logic Timeouts Telemetry RPC code
- 20. server client client client client client client
- 21. 🔥 wait ☺ 😰 🔥 🔥 wait ☺ 😰 🔥 ☺ ☺ ☺ ☺ ☺ ☺ ☺ ☺
- 22. 🔥 wait ☺ 😰 🔥 🔥 ☺ wait 😰 ☺ 🔥 🔥 wait 😰 ☺ 🔥 🔥 wait 😰 ☺ 🔥 🔥 …
- 23. 🔥 🗑
- 24. "I know, let’s have all circuit breakers share state”
- 25. "I know, let’s have all circuit breakers share state” Answer to the question “how did my application ended up importing a Zookeeper library again?"
- 26. Circuit breakers Timeouts Your code looks like this now Biz Logic Timeouts Telemetry RPC code Distributed state
- 27. server client 🔥🔥 🔥 server server serverserver 🔥🔥 🔥💩 🤔 Which instance should we talk to? ☺
- 28. DNS be like… '
- 29. "I know, let’s have clients keep track of healthy instances”
- 30. Circuit breakers Timeouts Your code looks like this now Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery
- 31. And that’s just for RPC reliability.
- 32. What makes 2017 different?
- 34. Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery SDK
- 35. Applica,on Transport Internet Network Circuit breakers Telemetry RPC code Distributed state Client-side Service Discovery }TCP/IP }? One way to think about it
- 36. But how does one go about adding a new layer to the TCP/IP stack?
- 37. Sidecars to the rescue Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery SCARY OUTSIDE WORLD
- 38. Sidecars to the rescue Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery SCARY OUTSIDE WORLDSidecar
- 39. Sidecars to the rescue
- 41. How does that impact your service?
- 42. Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery Service Plaform
- 45. Timeouts Biz Logic Stability Service Plaform Capacity Security Availability
- 47. Allows our services to pretend some of those are true
- 48. It’s not that these pa9erns aren’t used anymore, it’s just that the dumb work moved down the stack.
- 49. New, optmised, protocols are quite opaque (e.g. gRPC and friends) Works be9er with metadata-rich protocols
- 50. It makes it even harder to fully replicate produc,on earlier in the development cycle Coupled to the plaform
- 51. Not everything will be part of the mesh, i.e. the network s,ll isn’t homogeneous Leaky abstrac,on
- 52. Q&A