Skip to main content

From Monolith to Microservices: A Platform Engineer's Honest Take

· 2 min read
Saikoushik Gandikota
Saikoushik Gandikota
Senior Platform Engineer

"We're moving to microservices."

Every time I hear this, my first question is: "Why?" And in about half the cases, the answer boils down to "because everyone else is."

Here's what nobody in the microservices evangelism camp tells you: you need a platform to make microservices work. Without one, you're trading one set of problems for a worse set.

What the Monolith Actually Gave You​

  • One deployment process — simple, repeatable, understood
  • One database — joins are easy, transactions are ACID
  • One codebase — grep works, debugging is straightforward
  • One team — everyone understands the whole system

That's not technical debt. That's simplicity. And simplicity has enormous value.

What Microservices Actually Demand​

For each service you extract, you now need:

  • Its own CI/CD pipeline
  • Its own deployment configuration
  • Service discovery and load balancing
  • Inter-service authentication
  • Distributed tracing (because debugging across 15 services with console.log doesn't work)
  • A strategy for data consistency across services

Multiply that by 20 services. That's not an application problem anymore — it's an infrastructure problem. It's a platform problem.

When Microservices Make Sense​

  1. Independent scaling — one component needs 10x the compute of others
  2. Independent deployment — teams are blocked waiting for each other's releases
  3. Independent technology — one component genuinely needs a different language/runtime
  4. Organisational structure — you have autonomous teams that own distinct business domains

If none of these apply, you probably don't need microservices. You need a well-structured monolith.

The Platform Engineer's Role​

If the organisation IS going to microservices (and they usually are, regardless of advice), the platform team's job is to make the operational complexity invisible:

  • Service templates — new service in minutes, not days
  • Shared observability — every service ships telemetry from day one
  • Standardised networking — service mesh or API gateway, managed centrally
  • Golden paths — the easy way IS the right way

Without this, microservices become a distributed monolith — all the complexity, none of the benefits.

Has your microservices migration actually delivered value? Honest answers only — connect on LinkedIn.