It is not just Microservices
summary
Claims that microservices succeed only with matching ops and org changes and gives concrete evidence: a team pushes to production every 3.5 minutes, operates ~300 services (Netflix example ~600 services), and uses a Kafka event bus with lightweight “river” filter services plus per-service local databases instead of one central RDBMS. Uses Docker containers for ephemeral workloads and advocates replacing specialist titles with a system developer path, one-week horizons, experimentation-driven features, and business metrics as the primary measure.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:49Freds background
- 1:56Conferences
- 3:50Why do we care
- 6:56Competition
- 10:27How long does it take
- 12:34Valley Tech
- 15:43Microservices
- 18:09Event Buses
- 22:21Incremental Applications
- 26:53Open Source
- 29:48Requirements vs Stories
- 34:15We are smart
- 34:31Over specialization
- 36:02Competency pyramid
- 40:07Dedicated leadership
related talks
48mChallenges in Implementing MicroServices
49mChallenges in Implementing Microservices
50mChallenges in Implementing Microservices
01h 18mIn Defense of Microservices
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
08mThe Evolution of Microservices Architecture in Cloud-Native
37mKnee Deep in Microservices
25mMaking microservices a behaviour not a buzzword