May 3
Loading video player...
Microservices aren't defined by size — they're defined by independent deployability. And most teams arguing about them don't actually have the problem they solve. In 7 minutes: the strongest argument FOR, the strongest argument AGAINST, and the three questions that decide it for your team. In this video: → The one defining property — independent deployability (everything else is downstream) → The case FOR, steelmanned: the Amazon API Mandate, and Conway's Law → The case AGAINST, steelmanned: tail-at-scale math, and the "distributed monolith" failure mode → The three-question decision ladder — team count, deploy cadence, separable domains → Why some of the most trafficked sites in the world still run monoliths Next time the architecture debate starts at your company, write three questions on a whiteboard first. References: → Sam Newman, "Building Microservices" (2nd ed.) — https://samnewman.io/books/building_microservices_2nd_edition/ → Martin Fowler, "MonolithFirst" — https://martinfowler.com/bliki/MonolithFirst.html → Dean & Barroso, "The Tail at Scale" (CACM 2013) — https://www.barroso.org/publications/TheTailAtScale.pdf → Uber Engineering, "Domain-Oriented Microservice Architecture" — https://www.uber.com/blog/microservice-architecture/ → Adrian Cockcroft, Netflix microservices retrospective — https://www.infoq.com/presentations/microservices-netflix-industry/ #microservices #softwarearchitecture #systemdesign