Custom program
Distributed systems courses for engineers and technical leads
A magazine-paced syllabus for mid-level developers and technical leads expanding from single-service systems to broader architectures—rooted in South Korean operational realities, taught in English.
System map
The diagram below is schematic: ingress, async spine, cache skirt, observability taps. Names stay generic so you can map them to your stack.
Design tradeoffs
- Sync vs async seams: We bias toward explicit handoffs—even when it bruises ego.
- Cache warmth vs freshness: TTL ladders must show seasonal traffic, not a single number.
- Trace depth vs cardinality: Trace budgets are negotiated with product, not hoarded by SRE alone.
Workshop agenda (sample week)
- Mon: Ingress reality check + diagram redlines.
- Tue: Queue semantics lab with tabletop timelines.
- Wed: Cache TTL ladder with skew radar overlays.
- Thu: Resilience rehearsal with comms script.
- Fri: Gallery walk with rubric scores and mentor notes.
Mentor panel (rotating)
Architecture instructor
Haneul Park
Boundary rubrics, wall-sized templates.
Systems reviewer
Sora Kwon
Async choreography, poison flows.
Seminar moderator
Daeun Choi
Timeboxed critiques, calm incidents.
Technical FAQ (distinct from sitewide FAQ)
Do you standardize on one message broker?
No. We teach semantics first, then map to your broker vocabulary in office hours.
Will you sign NDAs for diagrams?
Yes, with lead time—email hello@surgenet.one before sharing sensitive maps.
What is still your responsibility after class?
Paying vendors, securing keys, and production approvals remain with your organization—we supply rehearsal craft, not outsourcing.