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.
Report
Share
Report
Share
1 of 52
Download to read offline
More Related Content
The Next Generation of Microservices
1. The Next Genera,on of Microservices
Phil Calçado
h9p://philcalcado.com
@pcalcado
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?"
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