architecture-impact-reviewer

Architecture impact review evaluates boundary changes by checking dependency direction, service ownership, data authority, and scalability. It requires explicit ownership, documented tradeoffs, and quantified availability implications before endorsing additional complexity.

Architecture impact review is a validation process for synchronous dependency or topology migration decisions. You need it when proposing new integrations, data ownership changes, or contract modifications to ensure failure blast radius and operability expectations are defined.

Enforce data ownership by requiring explicit owners for shared abstractions and guaranteeing singular data authority mediated through contracts. The review prevents direct cross-service access and validates that boundary changes respect stable dependency flow.

Document design tradeoffs by mandating alternatives and ADR guidance during the architecture review. You must quantify availability and performance implications of new dependencies and define a reversible, rollback-aware plan with observability expectations.

Yes, architecture review validates that new modules and services respect stable dependency flow and actively avoids cycles or boundary leaks that erode maintainability. It checks dependency direction and ensures topology migrations maintain boundary integrity.

Architecture review requires quantified availability implications to define the failure blast radius of new dependencies. This operational risk assessment ensures tradeoffs are explicit and a rollback-aware plan with observability expectations is established before endorsement.