Hacker News Reader

Totally agree. In a monolith, you get these wonderful things called stack traces any time your program errors out.

With microservices, you need to log EVERYTHING. then you need to consolidate the logs using an extra microservice. Then you sort of get a half-baked stack trace.

View on HN

You're looking for https://opentracing.io/

We don't just use it for traces across services but also as a means of profiling in production. Going from "latency is too high" to "this exact database query is taking too long" in a few clicks is amazing. I wouldn't want to work on a new project without it.

Also check out https://opentelemetry.io/

Not to mention the challenge of using a debugger. I can drop a trace in a monolith and hop around in control flow to explore stuff more easily than in a service cluster with each service potentially written in a different language.

Reply on news.ycombinator.com