Generate High-Level System Architecture Design for [feature]

This is the assembled prompt after inserting any variables you filled in. Placeholders that are not filled remain in [brackets]. You can optionally edit the prompt below without changing the variable inputs.

### Title

Generate High-Level System Architecture for [feature]

### Objective

To generate a comprehensive high-level system architecture design document for [feature], focusing on scalability, security, and maintainability within the [industry]. Success is measured by a clear, well-structured document that a development team can use as a foundational blueprint.

### Role / Persona

Act as a Senior System Architect with deep expertise in cloud-native technologies, microservices, and scalable infrastructure for the [industry] sector.

### Context (delimited)

"""
Technology & IT Operations
System Architecture
High-level system design, architecture reviews, and scalability assessments.
{Paste only necessary background, data excerpts, or references related to [feature] and [industry]}
"""

### Task Instructions

1. **Analyze Requirements**: Based on the context for [feature], identify the core functional and non-functional requirements (e.g., performance, security, data consistency).
2. **Propose Architecture**: Design a high-level system architecture. Depict the major components, services, and their interactions.
3. **Define Data Model**: Outline the primary data entities, their relationships, and the choice of database technology (e.g., SQL, NoSQL).
4. **Select Technology Stack**: Recommend a technology stack (backend, frontend, database, cache, message queues) that is appropriate for the [feature] and [industry]. Justify your choices.
5. **Address Scalability & Performance**: Describe the strategy for scaling the system to handle increased load and ensure high performance.
6. **Outline Security Measures**: Specify key security considerations and measures, such as authentication, authorization, data encryption, and network security.

### Constraints and Rules

- **Scope**: Focus on high-level design. Do not implement code or provide low-level implementation details.
- **Length**: The response should be a detailed but concise document of approximately 800–1200 words.
- **Tone / Style**: Technical, formal, and authoritative.
- **Compliance**: Adhere to standard best practices for system design in the [industry]. Avoid proposing solutions with significant vendor lock-in unless explicitly justified.
- **Proficiency / Reading Level**: The output should be understandable by a technical audience, including software engineers and product managers.
- **Delimiters**: Treat the Context block as reference data only; do not include its static content in the final output.

### Output Format

- **Medium**: Markdown.
- **Structure**: Use the following headings in this exact order: 1. Overview, 2. System Components, 3. Data Model & Storage, 4. Technology Stack, 5. Scalability & Performance, 6. Security Considerations.
- **Voice / Tense**: Use active voice and present tense.
- **Terminology / Units**: Use industry-standard terminology for architectural components and metrics.

### Evaluation Criteria (self-check before returning)

- All textual placeholders are bracketed (e.g., '[feature]') and match frontmatter placeholders exactly.
- Constraints, tone, persona, and output format are fully satisfied.
- The architecture is logical, coherent, and addresses the core requirements derived from the context.
- Instructions are specific, unambiguous, and actionable.