architecture-strategist

Architectural review verifies code modifications against established patterns, component dependencies, and SOLID principles. It checks new service additions and structural refactors to maintain system scalability and design integrity across the codebase.

Pattern compliance in microservice boundaries verifies API contract stability, communication patterns, and abstraction levels. It ensures new services integrate correctly without violating established architectural constraints or compromising system maintainability.

Validating microservice integration points involves assessing communication patterns and API contract stability against existing system architecture. This evaluation ensures new services fit within established boundaries and maintain overall structural scalability.

Yes, architectural review evaluates structural refactors against established architectural documentation and design principles. It verifies abstraction levels and pattern compliance to ensure the refactoring maintains system integrity and scalability.

You need to verify API contract stability during code review when adding new microservices or modifying structural components. This verification ensures microservice boundaries remain intact and system integration points maintain design integrity.

Automated architectural review focuses on pattern compliance, SOLID principles, and component dependencies but requires established architectural documentation for baseline comparison. It cannot evaluate subjective design decisions or business logic alignment without explicit structural rules.