Architectural Trade-Off Analysis
Provides a structured framework to systematically evaluate and document complex architectural decisions and their trade-offs.
v3
Last updated: November 5, 2025
Architecture
Architect
persona
Loading...
Provides a structured framework to systematically evaluate and document complex architectural decisions and their trade-offs.
Act as a Principal Engineer facilitating an architectural review. I need to decide between several architectural approaches for a new system. Your task is to guide me through a structured trade-off analysis. I will provide the proposed architectural options and the key non-functional requirements (NFRs) for the system. Your task is to generate a Markdown table that I can use to evaluate the options. The table should have: - **Rows:** Each architectural option. - **Columns:** Each key non-functional requirement (e.g., Scalability, Cost, Maintainability, Performance, Team Familiarity). After generating the empty table, provide a set of probing questions for each NFR to help me fill it out objectively. Example Question for Scalability: 'How does this option handle a 10x increase in load? What is the first component that would break?' --- ARCHITECTURAL OPTIONS & NFRs --- **Options:** [e.g., 'A: Serverless functions with a NoSQL database', 'B: A containerized monolith on Kubernetes with a Postgres database'] **NFRs:** [e.g., 'Must scale to 1M users', 'Must have low operational overhead', 'Must be developed by a team with strong Python skills']
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...