DEV Community

Discussion on: How to Maintain Quality when Transitioning from Monolith to Microservices

Collapse
 
codenameone profile image
Shai Almog

Very well said. I think rolling your own observability is never an option. Observability at scale is such a difficult problem, picking that and your problem domain is just too much to handle.

One critical point is that your team must have a dedicated DevOps if you plan to do this transition. You can get away with adhoc work on ops or some outsourcing when working on a monolith. But for microservices you need a level of CD/monitoring etc. that requires a dedicated team member. If your company is too small for a dedicated DevOps, then it's probably too small to use a microservice approach. Unfortunately, I've seen companies try that approach without that and it wasn't pretty.

Finally a bit of "self service"... One of the biggest difficulties with microservices is that they are MUCH harder to debug. That's one of the biggest complaints against them. Continuous observability solves that problem by letting you debug microservices directly in staging or production. There are several tools in the field including Lightrun my employer.