proomt

Search

Search posts, papers, and topics

Hall of Fame

Hall of FameBenjamin H. Sigelman et al.201043 min readpaperadvanced

Dapper, a Large-Scale Distributed Systems Tracing Infrastructure

Summary

Dapper is Google’s production‑grade distributed tracing system that achieves low overhead and ubiquitous deployment by instrumenting only a few core libraries and using adaptive sampling. The paper details its data model, sampling strategy, and the ecosystem of analysis tools built on top of it.

  • Adaptive sampling (≈1 in 1,000 requests) keeps overhead sub‑1% while still providing useful traces.
  • Instrumentation is confined to common threading, control‑flow, and RPC libraries, making tracing transparent to application code.
  • Spans are identified by probabilistically unique 64‑bit IDs and organized into tree structures for end‑to‑end request reconstruction.
  • Trace data is ingested and made queryable within a minute, enabling rapid production incident diagnosis.

Teams building large‑scale services can adopt Dapper’s design principles to get low‑impact, always‑on tracing without burdening developers.

8/10

Related reading

  1. Accelerating the borderless Lakehouse: Announcing preview of cross-cloud caching

    Google Cloud previewed cross‑cloud caching for its Borderless Lakehouse. The feature caches sub‑file Parquet blocks in Google Cloud, encrypts them with GMEK, isolates cache per tenant/region, and validates freshness via metadata checks. In tests it can reduce cross‑cloud data transfer to <5% of the original size, lowering query latency and cost for Iceberg tables stored in other clouds. BigQuery…

    Google Cloud Bloggoogle.com3 minrelease
  2. The Tail at Scale

    The paper defines “tail‑tolerant” systems that keep interactive latency (≤100 ms) low even as services scale to thousands of servers, and surveys the main causes of latency outliers. It shows that techniques such as request replication, hedged requests, and resource isolation can dramatically shrink the latency tail with modest overhead, enabling higher utilization without over‑provisioning.

    Hall of Fameresearch.google1 minpaperHN2
  3. Borg, Omega, and Kubernetes

    Google developed three container management systems: Borg, Omega, and Kubernetes, over a decade. This article details their evolution, design principles, and the lessons learned from managing containers at scale, emphasizing the shift from machine-oriented to application-oriented infrastructure.

    Hall of Famegoogleusercontent.com25 minpaperHN2
  4. OpenTelemetry everywhere: Migrating a metrics platform at scale

    Atlassian replaced its decade‑old gostatsd‑based metrics pipeline with a fully OpenTelemetry‑based stack by keeping the StatsD‑UDP contract on the client side and swapping in purpose‑built OTel Collector distributions for collection, ingest, aggregation, and forwarding. The migration was done incrementally, saved ~3.9% CPU per service, cut sidecar cost ~30% fleet‑wide, halved aggregation CPU, and…

    CNCFcncf.io6 minHN1