Latency Cartography Studio
Learn to turn application analytics into infrastructure latency maps you can defend in front of peers — without pretending every millisecond is already instrumented.
Learning outcomes
- Separate queue time, network time, and serialization time in a shared legend.
- Draft a multi-hop map with measured vs inferred segments clearly marked.
- Choose probes that answer a release question rather than collecting vanity timings.
- Facilitate a 15-minute map reading for mixed product and platform audiences.
Informational price: Cartography Seat from ₩1,150,000 — see pricing. No online checkout.
Modules
- Week 1 — Vocabulary of waiting Align on hop types, clocks, and what “p95” can and cannot say.
- Week 2 — Edge and first byte Map DNS, CDN, and TLS waits with synthetic and RUM cues.
- Week 3 — Service traversal Read spans across gateways and workers; label fan-out honestly.
- Week 4 — Dependency gravity Datastores, locks, and third parties — including the queue vs network module teams cite often.
- Week 5 — Probe craft Design checks that reveal regional drift without flooding backends.
- Week 6 — Defend the map Live critique, revision, and a take-home checklist for incidents.
Instructor
Sora Kim
Former platform lead; teaches latency literacy from the Infraedgenet studio in Korea.
Sora focuses on readable diagrams over tool evangelism. Cohorts stay small so critique time is real.
Who it fits
SREs, platform engineers, and senior backend developers who already have telemetry but lack a shared map language. You should be comfortable reading traces; we will not teach programming from scratch.
FAQ
Do I need a specific APM vendor?
No. Bring whatever produces timings you trust. We work in vendor-neutral map notation.
Is there a real limitation I should know?
Yes: if your organization forbids exporting even anonymized timings, you will practice on our sample paths instead of your production system. That still builds skill, but your final map will be less tailored.
How much weekly time?
Plan for one live session plus three to five hours of mapping homework. On-call weeks feel tighter — we allow one deferred critique.
How do refunds work?
See the Refund Policy before you enroll.
Reviews from this course
The queue vs network module stopped our Slack loops. Critique of my first map stung a little — and fixed the legend.
★★★★☆Strong facilitation. Week four’s datastore lab needed clearer prep notes; office hours covered the gap.