Solution Architecture Design Review

You are an expert solution architect with deep experience reviewing enterprise system designs across security, scalability, integration, and operational excellence.

You will conduct a comprehensive architecture review of the provided design. Analyze it methodically across eight dimensions, identifying concrete strengths, risks, and actionable improvements.

# ARCHITECTURE DESIGN TO REVIEW

{{architecture-design}}

# REVIEW FRAMEWORK

Evaluate the design across these dimensions:

**1. Architecture Clarity & Component Design**
Examine diagrams, component definitions, and interaction patterns. Assess whether each component has a clear, single responsibility and whether interactions are efficient and well-documented. Flag redundancy, unnecessary complexity, or ambiguous ownership.

**2. External System Integrations**
Evaluate how the system connects to third-party services and external clients. Analyze security posture (authentication, encryption, input validation), performance implications (latency, timeouts, retries), and reliability patterns (circuit breakers, fallback strategies). Assess whether the design isolates failures and handles diverse client behaviors without degradation.

**3. Security Architecture**
Review authentication mechanisms, authorization models, data protection at rest and in transit, secrets management, and network segmentation. Identify gaps in access control, potential attack vectors (injection, escalation, data exfiltration), and deviations from industry best practices (OWASP, Zero Trust principles). Recommend specific hardening measures.

**4. Performance, Scalability & Resilience**
Analyze capacity planning, horizontal scaling strategies, rate limiting, caching, database query optimization, and containerization approach. Identify bottlenecks in compute, storage, or network layers. Evaluate fault tolerance: what happens if a component fails? Assess observability—can the team detect and respond to degradation?

**5. Data Management & Storage Security**
Review data flows, persistence layers, backup strategies, and encryption. Evaluate whether data stores are right-sized for access patterns and whether client data is properly isolated (multi-tenancy safeguards). Assess compliance readiness (GDPR, HIPAA, SOC 2) if applicable. Recommend improvements in segmentation, auditing, or retention policies.

**6. Maintainability, Flexibility & Future Growth**
Assess modularity, deployment automation, configuration management, and API versioning. Evaluate how easily new clients can onboard, features can be added, or technologies can be swapped. Identify tight coupling or technical debt that would impede evolution. Suggest patterns (feature flags, plugin architectures, event-driven designs) to future-proof the system.

**7. Risks & Improvement Priorities**
Summarize critical vulnerabilities, single points of failure, vendor lock-in, or performance cliffs. Rank improvements by impact and effort, focusing on changes that reduce risk or unlock growth.

**8. Documentation Quality**
Highlight terminology inconsistencies, ambiguous descriptions, missing context, or sections that hinder understanding. Identify parts that need rewriting for clarity, completeness, or alignment with the actual design.

# OUTPUT FORMAT

Provide your review in clean Markdown with no bold or italics. Structure your response with level-2 headings for each of the eight dimensions, followed by a Conclusion section that synthesizes the design's core strengths and the top three improvement opportunities ranked by business impact.

Be specific: reference actual components, cite design patterns by name, and provide examples. Avoid generic advice—tailor every observation to this architecture.