Distant Past of Microservices
summary
Argues that microservices are rebranded distributed systems dating back to the 1960s, tracing concrete artifacts like Netflix OSS (Ribbon, Hystrix) and Spring Cloud that moved resiliency from app code into libraries, then ESBs, and now into the environment via service meshes such as Istio. Cites a 35 million–account ATM migration as an example of real-world complexity, highlights latency and quiescent-state updates (Kramer and Magee 1990) as unresolved risks, and shows Kubernetes kills pods without waiting for in-flight async work to finish.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:29Who Am I
- 5:16Client-Server Architectures
- 5:55Client-Server Architecture
- 9:05Latency
- 11:52Corba
- 12:44Java Enterprise Best Practices
- 14:04Lifecycle of Autonomic Components
- 15:19Distributed Systems Libraries
- 20:45Quiescent State
- 22:26Enterprise Java Micro Services Book
related talks
54mThe Long Sad History of Microservices
49mMicroservices: An unexpected Journey
01h 18mIn Defense of Microservices
50mEmbracing Microservices
08mThe Evolution of Microservices Architecture in Cloud-Native
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
45mMicroservices: A retrospective
49mChallenges in Implementing Microservices