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>