Superseded
Microservices promised independent deployment, technology heterogeneity, and organizational alignment (one team per service). Netflix's success story became the template for the industry.
Between 2014 and 2020, "decompose into microservices" became the default architectural prescription for scaling organizations. The pattern was sound for companies with Netflix-scale traffic and hundreds of engineering teams. It was misapplied by companies with five developers and moderate traffic.
Why it made sense: For large organizations, microservices solved real coordination problems — independent deployment, isolated failure domains, and team autonomy. The Conway's Law alignment (team structure mirrors system architecture) was genuinely powerful.
How it was superseded: By 2022, the industry had accumulated enough failure data to recognize the pattern's costs — distributed tracing complexity, network latency budgets, data consistency challenges, and operational overhead that exceeded the complexity of the monolith it replaced. Amazon's Prime Video team famously moved from microservices back to a monolith in 2023, reducing costs by 90%.
The lesson: Microservices are a scaling strategy, not a quality strategy. Applying them before the organization's coordination costs exceed the system's complexity costs creates distributed complexity without distributed benefit. The architecture that solves Netflix's problems creates new problems for a 10-person startup.