Architecture Review

You are a senior software architect and technical lead.

Category
Software Development & Coding
Output
Markdown
Fields
4
  • software-development
  • technical-explanation
  • performance-optimization
  • database-design
  • cache-strategy
  • risk-assessment
  • design-review

Fill in the details

Briefly describe the application, its core purpose, and target users.

List the programming languages, frameworks, databases, and cloud services you plan to use.

Outline the key features, user flows, and business rules the system must support.

Describe your expected traffic growth, peak load targets, or 10x/100x scaling expectations.

Prompt

You are a senior software architect and technical lead. Review the proposed system design below and provide a structured, actionable architectural assessment. **System Details:** - Description: System description - Technology stack: Technology stack - Main requirements: Main requirements - Scaling goals: Scaling goals **Instructions:** Analyze the provided details and deliver a concise architectural review covering exactly these five areas: 1. **Architecture Patterns:** Recommend the most suitable patterns (e.g., MVC, Microservices, Event-Driven, Serverless) and justify your choices based on the requirements. 2. **Weaknesses & Risks:** Identify potential bottlenecks, single points of failure, or design flaws in the current plan. 3. **Database & Caching Strategy:** Outline a recommended data modeling approach, storage choices, and caching layers to ensure performance and consistency. 4. **Security Considerations:** Highlight critical security aspects (authentication, authorization, data protection, network security) and suggest mitigation strategies. 5. **Scalability Plan:** Explain how the system would handle 10x and 100x load increases, including horizontal/vertical scaling, load balancing, and state management. **Constraints:** - Base all recommendations strictly on the information provided. Do not invent services, libraries, or constraints. - If a question cannot be fully answered due to missing context, list the specific missing details in a brief "Open Questions" section at the end instead of guessing. - Keep explanations concise, technical, and directly actionable for engineering teams. **Output Format:** Return a Markdown document with clear headings for each of the five areas, followed by the "Open Questions" section (if applicable). Use bullet points for readability.

How to use this prompt

  1. Fill in the fields above. Required ones are marked with *.
  2. Check the prompt preview: your answers appear highlighted in place.
  3. Select Copy prompt and paste it into ChatGPT, Claude, Gemini or any AI assistant.
See all Software Development & Coding prompts