Why Microservices Are Out and Monoliths Are Making a Comeback

For years, we were told microservices were the future.

“Split everything into tiny, independent services,” they said. “Scale teams independently. Deploy faster. Move faster.”

Image used under fair use. Sourced from Google. Not owned by the author.

But lately, something strange is happening. Teams that migrated to microservices are now going back to monoliths.

And it’s not just small startups — it’s Amazon, Shopify, Basecamp, Segment, and even Google.

Yep. The same folks who pioneered microservices are quietly admitting:

“We went too far.”

Wait… What’s Wrong With Microservices?

Let’s be honest. Microservices sound great. In theory, they promise:

• Independent deployments
• Scalable teams
• Clean separation of concerns

But here’s what you often get in reality:

• Hundreds of tiny repos nobody understands
• Latency issues from too much network chatter
• Devs spending more time on infra than product
• “Where the hell is this bug even coming from?”