Flagship course
Service Graph Observatory
Six live studios that turn application analytics for microservice dependency tracing into a weekly team habit.
Learning outcomes
Map a critical user journey as a dependency graph with explicit risk tags.
Choose sampling strategies that preserve rare-but-costly edges.
Facilitate a 30-minute dependency clinic for mixed stakeholders.
Write an incident narration that cites graph evidence without blame theater.
Modules
- Module 1 — Orient the mesh. Inventory services, owners, and the journeys that matter commercially.
- Module 2 — Spans to stories. Convert raw traces into readable paths; prune noise without losing signal.
- Module 3 — Fan-out clinic. Diagnose parallel calls, waiting edges, and false “healthy” aggregates.
- Module 4 — Sampling with ethics. Budgets, head-based vs. tail-based choices, and privacy constraints.
- Module 5 — Scorecards & rituals. Build a lightweight weekly review that survives calendar pressure.
- Module 6 — Stakeholder narration. Practice explaining dependency risk to product and finance partners.
Instructor
Soo-yeon Han
Former platform lead for a Seoul marketplace mesh of 120+ services. Soo-yeon now teaches dependency analytics full-time with Microservicex Digital, blending production war stories with calm studio pacing.
Informational pricing
₩1,280,000 per learner · Mesh Observatory tier
No checkout on this site. Seats are confirmed after a short intake call. See pricing for adjacent options.
Ask about the next cohortFAQ
Do I need a specific tracing vendor?
No. Labs are vendor-neutral. We reference OpenTelemetry concepts and common UI patterns so you can map them to your stack.
How much time each week?
Plan for one 90-minute live studio plus two to three hours of graph homework. Most learners finish in six weeks.
What is a real limitation of this course?
We do not deep-dive proprietary mainframe or heavily air-gapped collectors. Those environments need Platform Guild customization; the public cohort assumes you can export anonymized graphs.
Is there a certificate?
Optional. We issue one if your team needs it for L&D records; the work product that matters is your dependency ritual.
Course reviews
“The scorecard from Module 5 is still pinned in our Slack. Module 4 moved faster than our team could absorb — we rewatched twice.”
Yuna · Platform engineer, Daegu
★★★★☆ Completed Service Graph Observatory — “Strong on fan-out; lighter on message queues than I hoped.”
Client in media streaming