[{"data":1,"prerenderedAt":28},["ShallowReactive",2],{"blog-tag-en-microservices":3},[4,16],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\u002Fblog\u002Fen\u002Fkubernetes-microservices-chatty-calls-latency","One Order, Five Hidden Service Calls: The Real Cause of Latency in Kubernetes Microservices' \"Chatty Calls\"","A single checkout request was quietly triggering five separate service calls behind the scenes. The culprit isn't bad code — it's the \"chatty call\" architecture that Kubernetes microservices tend to fall into. This article explains the distributed N+1 problem and how to fix it.","2026-08-02",[10,11,12,13,14,15],"kubernetes","k3s","microservices","service-mesh","latency","managed-kubernetes",{"path":17,"title":18,"description":19,"date":20,"tags":21},"\u002Fblog\u002Fen\u002Fopentelemetry-distributed-tracing","Implementing Distributed Tracing with OpenTelemetry: From Basics to Production","A practical guide to distributed tracing with OpenTelemetry. Covers Collector setup, auto-instrumentation, Jaeger\u002FTempo integration, and Kubernetes best practices.","2026-05-27",[22,23,10,24,25,26,27,12],"opentelemetry","distributed-tracing","cncf","observability","jaeger","tempo",1792488967309]