Ji-hoon Lee
Lead analyst. Former platform engineering lead for a Korean retail group. Focuses on dependency mapping and release risk letters.
About
A Seoul practice for hard-to-see dependencies
App Architects exists for teams who know their applications are entangled — and need a calm, evidence-led way to see service dependencies and performance bottlenecks before the next release.
Origin
The practice started in Jongno-gu after years of release weeks derailed by call paths nobody had written down. We noticed that architecture conversations often jumped to tools and rebuilds before anyone had mapped the edges that actually failed under load.
App Architects stays deliberately small. Engagements are led by practitioners who have owned production services, not by a rotating bench of generalists reading slides into a room.
Working approach
We treat diagrams as hypotheses. Metrics, interface contracts, and incident notes decide which edges matter. Findings are ranked so engineering and leadership can argue about priorities with the same picture in front of them.
Office days happen near Gyeonghuigung. Remote weeks follow Seoul business hours unless we agree otherwise.
People you will meet
Yuri Han
Performance reviewer. Specializes in bottleneck ranking from traces and resource graphs, and in quarterly health-check cycles.
Values that show up in the work
- Specificity over slogans. Every finding names a path, an owner, or a missing measurement.
- Respect for your builders. We do not perform “gotcha” reviews; disagreements happen in workshops, not in surprise email threads.
- Scope discipline. If the estate is too large for one map, we phase it rather than blur it.