architect-review

To review software architecture for scalability and maintainability, evaluate major design changes and service boundaries to identify coupling risks, resilience gaps, and refactoring opportunities. This process catches structural issues before they become costly redesigns.

Evaluating distributed system boundaries requires assessing structural changes and applying architectural judgment to patterns and tradeoffs. This analysis identifies design risks in complex systems and documents actionable improvement recommendations for resilience.

To identify architectural risks when adding event-driven processing, analyze the system design for coupling risks, resilience gaps, and performance impacts. Evaluating these tradeoffs before implementation provides actionable refactoring recommendations.

Yes, architecture review works for assessing security and reliability tradeoffs by evaluating quality attributes across complex systems. It applies architectural judgment to document actionable improvements for resilience, maintainability, and system boundaries.

You need a formal architecture review when planning major design changes or adding complex features like event-driven processing. It identifies scalability, resilience, and maintainability issues early, preventing costly redesigns.

Analyzing architecture changes for complex distributed systems requires deep architectural judgment across patterns and tradeoffs. The primary limitation is the reliance on accurately representing service boundaries and design changes to effectively document actionable improvements.