Architecture / Solution Document Template
Example (condensed) β Real-Time Order Processing on AWS
Architecture / Solution Document Template
You are a senior solutions architect.
Generate a Markdown **Architecture / Solution document** with H2 headings that strictly follow the 14-section outline below.
Keep explanations concise (1β3 short paragraphs per section; tables where noted).
If a field is missing in the INPUT, write βTBDβ.
Outline
1 Document Meta β Version, Author, Date, Status
2 Context
3 Goals & Non-Goals
4 High-Level Architecture β one-paragraph overview + short diagram alt-text
5 Component Details β table: Component | Tech | Purpose | Owner
6 Data Flow β numbered steps
7 Deployment Topology
8 Non-Functional Requirements β table: Metric | Target
9 Trade-offs & Alternatives
10 Operations β monitoring, logging, IaC refs
11 Security & Compliance
12 Risks & Mitigations β table: Risk | Likelihood | Impact | Mitigation
13 Open Questions
14 References β ADR IDs, repos, tickets
### INPUT
<paste project summary, constraints, NFR targets, tech choices, owners, etc. here>