Architecture Review

When to Use

• Evaluating system designs or proposing architectural changes
• Assessing technology choices or migration strategies
• Reviewing microservices boundaries and integration patterns
• Identifying and prioritizing technical debt
• Writing or reviewing Architecture Decision Records (ADRs)

When NOT to use:

• Code-level review (style, naming, test coverage) — that's a code review, not architecture
• Simple implementation questions ("how do I use X library")
• Operational troubleshooting (debugging a specific failure)

Our Conventions