Downloaded 10 times
Uploaded byPhil Calçado
The Next Generation of Microservices — YOW 2017 Brisbane
The document discusses the evolution of microservices architectures over time as techniques were developed to address challenges introduced by highly distributed systems. Early approaches involved implementing circuit breakers, timeouts, and sharing state across services to handle failures. Later, service discovery and client-side load balancing were introduced. Today, sidecars and service meshes move reliability patterns lower in the stack and provide stability, security, and other features to services through a common platform. However, these abstractions also introduce new tradeoffs around opacity, development cycles, and homogeneity.
More Related Content
Similar to The Next Generation of Microservices — YOW 2017 Brisbane
The Next Generation of Microservices — YOW 2017 Brisbane
- 1. The Next Generationof Microservices Phil Calçado http://philcalcado.com @pcalcado
- 3. highly distributed application architecture Wecan think of microservices as
- 4. Highly distributed application architecturesare just a flavor of distributed computing
- 5. Technical Challenges Organization Challenges Introducing distribution intoyour architecture brings up new
- 6. Introducing distribution intoyour architecture brings up new
- 8. The example wewill work with today: Recovering from temporary failure
- 9.
- 11. "I know, let’suse microservices”
- 12. Timeouts Your code lookslike this now Biz Logic Timeouts
- 13.
- 14. Timeouts Your code lookslike this now Biz Logic Timeouts RPC code
- 15.
- 17.
- 18. "I know, let’simplement circuit breakers and timeouts”
- 19. Circuit breakers Timeouts Your codelooks like this now Biz Logic Timeouts Telemetry RPC code
- 20. server client client clientclient client client
- 21.
- 22. 🔥 wait ☺ 😰 🔥 🔥 ☺ wait 😰 ☺ 🔥 🔥 wait 😰☺ 🔥 🔥 wait 😰 ☺ 🔥 🔥 …
- 23.
- 24. "I know, let’shave all circuit breakers share state”
- 25. "I know, let’shave 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 codelooks like this now Biz Logic Timeouts Telemetry RPC code Distributed state
- 27. "I know, let’shave clients keep track of healthy instances”
- 28. server client 🔥 🔥 🔥 server server serverserver 🔥 🔥 🔥 💩 🤔 Which instance should we talk to? ☺
- 29.
- 30. Circuit breakers Timeouts Your codelooks like this now Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery
- 31. And that’s justfor RPC reliability.
- 32. What makes 2017different?
- 33.
- 34. Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPCcode Distributed state Client-side Service Discovery SDK
- 35. Application Transport Internet Network Circuit breakers Telemetry RPC code Distributedstate Client-side Service Discovery }TCP/IP }? One way to think about it
- 36. But how doesone go about adding a new layer to the TCP/IP stack?
- 37. Sidecars to therescue Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery SCARY OUTSIDE WORLD
- 38. Sidecars to therescue Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPC code Distributed state Client-side Service Discovery SCARY OUTSIDE WORLDSidecar
- 39. Sidecars to therescue
- 41. How does thatimpact your service?
- 42. Circuit breakers Timeouts Biz Logic Timeouts Telemetry RPCcode Distributed state Client-side Service Discovery Service Platform
- 43.
- 45.
- 46.
- 47. Allows our servicesto pretend some of those are true
- 48. It’s not thatthese patterns aren’t used anymore, it’s just that the dumb work moved down the stack.
- 49. New, optmised, protocolsare quite opaque (e.g. gRPC and friends) Works better with metadata-rich protocols
- 50. It makes iteven harder to fully replicate production earlier in the development cycle Coupled to the platform
- 51. Not everything willbe part of the mesh, i.e. the network still isn’t homogeneous Leaky abstraction
- 52.