CodingArchitectureadvancedFeatured

Architectural Decision Record (ADR) Analysis & Trade-Off Matrix

Evaluate competing technical architectures, state assumptions, and document a formal Architectural Decision Record.

#system-architecture #adr #trade-offs #software-engineering #decision-framework

Compatibility & Specs

Compatible AI Models

ClaudeChatGPTGemini

Last UpdatedOct 3, 2026

Customizable Variables3 parameters

Main Prompt Template3 Variables

168 words • 1397 characters

You are a Principal Enterprise Systems Architect. I need to evaluate competing architectural approaches for a major technical initiative and document the decision in a formal Architectural Decision Record (ADR). Context & System Requirements: [system_requirements] Key Non-Functional Constraints (Latency, Scale, Team Size, Budget): [non_functional_constraints] Architectural Options Under Consideration: [options_considered] Generate an exhaustive Architectural Decision Record (ADR): 1. Executive Summary & Context: State the architectural challenge, current technical baseline, and why an architectural decision is necessary now. 2. Deep Trade-Off Comparison Matrix: Compare the options across 6 dimensions: Latency/Throughput, Operational Complexity, Failure Modes & Blast Radius, Developer Velocity, Infrastructure Cost, and Migration Reversibility (one-way vs. two-way door). 3. The Chosen Decision & Justification: Select the recommended architecture and provide 3 definitive technical arguments justifying why it outperforms alternatives under our specific constraints. 4. Consequences & Mitigations: Document positive consequences, negative operational consequences (technical debt accepted), and specific mitigations. 5. Standard ADR Template Output: Deliver the formal ADR formatted in standard Nygard/Michael Nygard markdown syntax (Title, Status, Context, Decision, Consequences).

Tip:Variables marked in purple brackets can be tailored below.

Customize Prompt

Fill in the variables below. Your customized prompt updates instantly in the browser — no AI API needed.

Parameters (3)* Indicates required field

System Requirements*[system_requirements]

What the system or feature needs to do functionally

Non-Functional Constraints*[non_functional_constraints]

Scale, SLA, team bandwidth, infrastructure budget

Options Considered*[options_considered]

The specific architectural alternatives being evaluated

3 parameters active

Live Customized OutputLive Preview

246 words

You are a Principal Enterprise Systems Architect. I need to evaluate competing architectural approaches for a major technical initiative and document the decision in a formal Architectural Decision Record (ADR). Context & System Requirements: A multi-tenant background notification and webhook delivery pipeline that processes up to 25 million events per day with at-least-once delivery, exponential backoff retries, and customer-configured secret signing. Key Non-Functional Constraints (Latency, Scale, Team Size, Budget): P99 delivery under 3 seconds; 5-person engineering team with minimal dedicated DevOps support; budget capped at $2,500/month AWS compute spend. Architectural Options Under Consideration: Option A: Fully serverless AWS SQS + EventBridge + Lambda workers. Option B: Self-managed Redis Streams with autoscaling Go workers on AWS ECS. Option C: Managed Apache Kafka (Amazon MSK) with dedicated consumer services. Generate an exhaustive Architectural Decision Record (ADR): 1. Executive Summary & Context: State the architectural challenge, current technical baseline, and why an architectural decision is necessary now. 2. Deep Trade-Off Comparison Matrix: Compare the options across 6 dimensions: Latency/Throughput, Operational Complexity, Failure Modes & Blast Radius, Developer Velocity, Infrastructure Cost, and Migration Reversibility (one-way vs. two-way door). 3. The Chosen Decision & Justification: Select the recommended architecture and provide 3 definitive technical arguments justifying why it outperforms alternatives under our specific constraints. 4. Consequences & Mitigations: Document positive consequences, negative operational consequences (technical debt accepted), and specific mitigations. 5. Standard ADR Template Output: Deliver the formal ADR formatted in standard Nygard/Michael Nygard markdown syntax (Title, Status, Context, Decision, Consequences).

Launch in:

ChatGPT Claude Gemini

How to Use This Prompt

Follow this 3-step workflow to extract high-signal responses from any compatible AI model.

1. Tailor the Parameters

Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.

2. Send to AI Model

Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.

3. Review and Iterate

Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.

Prompt Variables & Parameters

Reference breakdown of every dynamic variable embedded in this prompt template.

Placeholder	Parameter Name	Type	Status	Description & Guidance
[system_requirements]	System Requirements	textarea	Required	What the system or feature needs to do functionallyDefault: A multi-tenant background notification and webhook delivery pipeline that processes up to 25 million events per day with at-least-once delivery, exponential backoff retries, and customer-configured secret signing.
[non_functional_constraints]	Non-Functional Constraints	text	Required	Scale, SLA, team bandwidth, infrastructure budgetDefault: P99 delivery under 3 seconds; 5-person engineering team with minimal dedicated DevOps support; budget capped at $2,500/month AWS compute spend.
[options_considered]	Options Considered	textarea	Required	The specific architectural alternatives being evaluatedDefault: Option A: Fully serverless AWS SQS + EventBridge + Lambda workers. Option B: Self-managed Redis Streams with autoscaling Go workers on AWS ECS. Option C: Managed Apache Kafka (Amazon MSK) with dedicated consumer services.

Example Execution & Benchmark Output

Sample input arguments and the verified AI response demonstrating expected quality and formatting.

Sample VariablesInputs

[system_requirements]

A multi-tenant background notification and webhook delivery pipeline that processes up to 25 million events per day with at-least-once delivery, exponential backoff retries, and customer-configured secret signing.

[non_functional_constraints]

P99 delivery under 3 seconds; 5-person engineering team with minimal dedicated DevOps support; budget capped at $2,500/month AWS compute spend.

[options_considered]

Option A: Fully serverless AWS SQS + EventBridge + Lambda workers. Option B: Self-managed Redis Streams with autoscaling Go workers on AWS ECS. Option C: Managed Apache Kafka (Amazon MSK) with dedicated consumer services.

Expected AI ResponseVerified Result

### Architectural Decision Record (ADR): Webhook Delivery Pipeline **Status:** Accepted **Date:** 2026-10-03 **Decision Makers:** Principal Architect, Backend Lead, DevOps Engineer #### 1. Context & Problem Statement We must deliver 25 million multi-tenant webhooks daily. Customer endpoints have unpredictable latency and high failure rates. We need durable queuing, retry backoff, and isolation so one slow recipient endpoint cannot exhaust workers and delay delivery for other tenants. #### 2. Trade-Off Evaluation Matrix - **Option A (AWS SQS + Lambda):** Operational complexity: Very Low | Cost at 25M calls: ~$3,200/mo (exceeds budget due to Lambda duration waiting on slow HTTP responses) | Isolation: High. - **Option B (Redis Streams + Go on ECS) [CHOSEN]:** Operational complexity: Low-to-Moderate | Cost: ~$850/mo (3 lightweight ECS Fargate tasks using non-blocking epoll Go HTTP clients) | Isolation: Moderate. - **Option C (Kafka / MSK):** Operational complexity: Very High | Minimum cluster cost: ~$2,000/mo | Overkill for a 5-person team without dedicated SRE. #### 3. Decision We choose **Option B (Redis Streams with Go workers on ECS)**. Go's lightweight goroutines allow each worker container to hold 10,000 concurrent outbound HTTP requests without memory exhaustion, keeping compute costs 70% below Lambda. #### 4. Consequences & Mitigations - *Negative:* Redis is in-memory; sudden cluster crash could lose un-persisted stream segments. - *Mitigation:* Configure Redis AOF with `appendfsync everysec` and multi-AZ replication. DLQ events overflow to S3 bucket.

Best Use Cases

Scenarios and roles where this prompt produces maximum leverage.

Staff and Principal engineers authoring RFCs and architecture decision documents

Engineering leads evaluating cloud infrastructure costs against team operational capacity

Distributed development teams documenting technical trade-offs for permanent record

Tips for Best Results

Techniques to elevate response fidelity

•Provide rich background context rather than one-sentence inputs to receive deep, non-generic responses.
•Engage in multi-turn conversation: use the initial output as a baseline, then ask the AI to sharpen specific sections.
•Prompt the model to highlight any hidden assumptions or missing trade-offs in its recommendations.

Common Mistakes to Avoid

Frequent failure modes and anti-patterns

•Giving minimal context and expecting nuanced, expert-level strategic output.
•Not validating factual references, citations, or statistical claims with verified primary sources.
•Skipping the customization step and pasting raw bracketed template variables into the AI chat.

Part of Curated Collections

This prompt is sequenced as part of these goal-oriented workflows

View all collections

Coding & Engineering

10 Prompts

AI Prompts for Software Developers

A systematic engineering toolkit covering technical design, edge-case testing, rigorous code review, and root-cause debugging.

#Architecture#Code Review+4

Explore Collection

Related AI Prompts

Complementary workflows in Coding

View all Coding prompts

Codingadvanced

Production Incident Post-Mortem & Root-Cause Synthesizer

Convert messy incident Slack logs and alerts into a blameless, rigorous post-mortem with corrective action items.

claudechatgptgemini

#post-mortem#root-cause-analysis#sre

View Prompt

Codingadvanced

Monolith to Modular Decoupling & Boundary Architect

Carve clear bounded contexts out of entangled monoliths using the Strangler Fig pattern and event-driven seams.

claudechatgptgemini

#software-architecture#refactoring#monolith-to-microservices

View Prompt

Next.jsadvanced

Next.js Server vs. Client Component Boundary Decision Matrix

Audit page trees to push 'use client' directives to the leaves, minimize JS bundles, and maximize server streaming.

claudechatgptgemini

#nextjs#server-components#client-components

View Prompt

Related Engineering Guides

Deep-dive playbooks and system prompt methodologies for Coding

View all guides

Prompt Engineering#promptarchitecture

8 min read

How to Write Better AI Prompts

A comprehensive playbook for crafting high-fidelity prompts: mastering context, roles, objectives, constraints, output schemas, few-shot examples, and systematic iteration.

Mar 25, 2026Read Guide

Software Engineering#engineering

9 min read

AI Prompts for Software Developers

Turn modern LLMs into senior engineering peers: tactical prompt patterns for architecture review, edge-case test generation, root-cause debugging, and technical documentation.

Mar 27, 2026Read Guide