1. Service Mesh advanced

    A platform is evaluating a service mesh. What should be checked before adopting, and what is the honest justification?

    2 min answer service-meshcomplexityobservabilitymtls
  2. Service Mesh advanced

    A platform runs 2000 pods across 300 services and is about to put a sidecar proxy in every pod. Roughly what does the fleet cost in memory and control-plane work before a single request is served, and which number grows fastest as the platform doubles?

    3 min answer service meshsidecarcapacitycontrol plane
  3. Service Mesh advanced

    A proposal for an internal tool serving 50 requests per second specifies a service mesh, distributed tracing, three databases, a message broker, distributed locks and multi-cluster deployment. What do you cut and what do you keep?

    3 min answer over-engineeringsimplicitymeshcritique
  4. Service Mesh advanced Multiple choice

    After a mesh rollout, one service's p99 rises from 30 ms to 70 ms, but only for calls to services in other namespaces. Same-namespace calls are unchanged. CPU on both sides is flat and the proxy reports no errors. What is the most likely cause?

    3 min answer service meshlatencylocalitycross-zone
  5. Service Mesh advanced

    WeChat's backend sheds overload with DAGOR, published at SoCC 2018: each service detects overload from the average queuing time of requests in its own pending queue - thresholded at 20 ms against a 500 ms task timeout - and rejects by admission level rather than by rate. A platform team running a service mesh asks why they cannot get this from the mesh's load-shedding settings. What did WeChat choose, why did it fit, and what does it cost?

    3 min answer tencentwechatdagorload-shedding