Why Tech Giants Are Turning Away from Microservices in 2023
In 2023, major tech companies like Google, Amazon, and Uber publicly questioned the benefits of microservices, revealing new architectural approaches that promise lower latency, reduced costs, and simpler deployment, while highlighting the challenges and pitfalls that have led many teams to revert to monolithic designs.
2023 was dubbed the “year of microservices reversal.” Long‑standing belief that microservices are the default cloud‑native architecture began to crumble as leading companies publicly criticized the model.
Google’s engineers argued that splitting applications into independently deployable services often backfires, creating more challenges than benefits. In a paper titled “Towards Modern Development of Cloud Applications,” they described microservices as a boundary‑less structure that conflates logical and physical boundaries.
Google proposes a “Microservices 2.0” approach: build applications as logical monoliths but let an automated runtime decide where and how to run workloads. Their experiments showed up to 15× lower latency and 9× lower cost.
Amazon’s Prime Video team similarly abandoned serverless and microservices for a monolithic architecture, cutting operational costs by over 90 % and simplifying scaling. Their experience highlighted that serverless orchestration (AWS Step Functions) introduced scaling limits and high charges.
Other companies, such as Uber, have also faced microservice fatigue. Uber’s early microservice sprawl led to monitoring, testing, CI/CD, and SLA complexities. They later consolidated services, assigning 5‑10 engineers per business‑function service and emphasizing the need to choose the right solution at the right time.
Managed by Q, a SaaS provider, moved to microservices only to discover that each new service added infrastructure overhead and increased development effort, eventually merging many services back into larger units.
These cases illustrate a broader trend: the perceived benefits of microservices—performance, traceability, manageability, and API stability—are often offset by real‑world costs and complexity. Many teams now view microservices as a “distributed monolith” that fails to deliver on its promises.
Google’s new approach separates programming and deployment concerns, allowing developers to write logical monoliths while the runtime optimizes execution for cost and performance.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java High-Performance Architecture
Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.