아키텍처 가이드
리뷰하는 쪽에서 쓴 실전 가이드입니다. 수백 건의 클라우드 아키텍처 리뷰에서 배운 것을 담았습니다. 특정 회사 이야기는 없고, 어디에나 적용되는 질문과 패턴, 템플릿만 있습니다.
가이드는 영어로 되어 있습니다.
- 가이드 1 The Architecture Review Checklist: 41 Questions I Ask The questions that come up in almost every cloud architecture review I run — compute, ownership, security, data, networking, resilience, operations and cost — as a checklist you can use before yours.
- 가이드 2 How to Prepare for an Architecture Review What to bring to a cloud architecture review so it's one meeting, not three: entry criteria, the diagrams reviewers need, the cross-cutting concerns people forget, and how to handle open questions.
- 가이드 3 The Compute Ladder: Serverless-First, Then Work Backwards A simple order of preference for where code runs — SaaS, serverless, containers, servers — why each rung up removes work, and how to design the ideal version first and only step down for a real constraint.
- 가이드 4 Cloud Architecture Anti-Patterns (and What to Do Instead) Seventeen patterns I flag again and again in cloud architecture reviews — glue-code functions, synchronous long jobs, polling, credentials on disk, jump hosts — each with the alternative I recommend.
- 가이드 5 Architecture Diagrams and Decision Records Reviewers Trust How to draw cloud architecture diagrams that answer questions before they're asked, and a lightweight architecture decision record (ADR) template for the choices you'll be asked to defend.
- 가이드 6 Guardrails and Paved Roads: Scaling Cloud Architecture Across Teams How a central cloud team can help dozens of teams build well without becoming a bottleneck: configuration as a service, compliance as code, reusable IaC constructs, identity-based segmentation and small blast radii.