It's Simple...
summary
Argues that breaking monoliths into microservices reduces overall complexity by enforcing interfaces, cites Netflix OSS and an org-driven architecture, reports the culture deck PDF hitting 15 million views, and describes running identical code across three zones nine regions so services survive region loss. Recommends developers be on-call to cut mean time to repair, favor product teams over projects to avoid long lock‑in cycles, and measure success by shortening feedback loops from years to weeks so teams learn and iterate faster.
AI-written summary · about
chapters (13)
- 0:00Start
- 6:13What is the meaning of life, the universe... and everything?
- 7:39What's the most complicated thing you deal with intuitively?
- 14:46Imposing process drives away talent.
- 17:50The basic thesis of this article is that organizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations.
- 20:00Systems are simple and flexible.
- 23:07Simplify the things we build.
- 28:08Optimize for the customers you want to have
- 29:23Monolithic apps only look simple from the outside.
- 30:24Microservices enforce separation that makes them less complicated.
- 33:10Innovate Leverage Commoditize
- 33:58Clear concept Too many choices Mainstream adoption
- 34:35Compatible implementations as a service
related talks
50mEmbracing Microservices
38mIt's Simple…
57mBuilding Systems that are #neverdone
46mLove Your Monolith
43mMonolith? Microservices? Who cares?
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
48mIT Architecture : All your micro-services are wrong PERIOD!
47mMicroservices? Monoliths? An Annoying Discussion!