Skip to main content
MethodTechnology & DevelopmentApp & web developmentAdvanced

Design a software system architecture

An architecture with components, data flow, scaling, failure handling and trade-offs.

This is a practical, copy-paste process for designing a new service or scaling an existing one.. Use it when you want a clear structure, then add your own details and the linked evidence.

Published by Deepstory Research. Reviewed Sep 2026.

How to use this method

  1. 1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
  2. 2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
  3. 3. Add evidenceAttach the evidence files listed on this page so the AI works from sourced numbers, not guesses.

The prompt

Paste it as-is. The AI will ask for anything still in [BRACKETS].

Download .md
# Design a software system architecture
Method by Deepstory Research: deepstoryresearch.com/method/system-design

You are a staff software engineer. Follow the method below step by step. Goal: An architecture with components, data flow, scaling, failure handling and trade-offs.

## My inputs
- System goal: [SYSTEM_GOAL]  (example: real-time price alerts for 100k users)
- Requirements: [REQUIREMENTS]  (example: latency, availability, cost)
- Existing stack: [EXISTING_STACK]  (example: describe)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. Clarify functional and non-functional requirements.
2. Estimate load.
3. Propose components and data flow.
4. Choose storage and messaging.
5. Address scaling, failures, observability and security.
6. List trade-offs and alternatives.

## Deliver the output in this structure
- Requirements
- Capacity estimate
- Architecture (text diagram)
- Component details
- Failure modes
- Trade-offs

## Quality rules
- Justify every component; remove any that is not needed.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

What you need to give the AI

InputPlaceholderExample
System goal[SYSTEM_GOAL]real-time price alerts for 100k users
Requirements[REQUIREMENTS]latency, availability, cost
Existing stack[EXISTING_STACK]describe

Use it when

  • Designing a new service or scaling an existing one.

What you get

  • Requirements
  • Capacity estimate
  • Architecture (text diagram)
  • Component details
  • Failure modes
  • Trade-offs

The procedure, step by step

Read this before you run it, so you can check the AI actually followed the method.

  1. 1

    Clarify functional and non-functional requirements.

  2. 2

    Estimate load.

  3. 3

    Propose components and data flow.

  4. 4

    Choose storage and messaging.

  5. 5

    Address scaling, failures, observability and security.

  6. 6

    List trade-offs and alternatives.

Quality checks built into the prompt

  • • Justify every component; remove any that is not needed.
  • • Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].

Evidence to use with this method

Methods tell the AI how to think. Evidence gives it sourced numbers to think with. Download a context file and attach it with the prompt.

Run next

Methods that chain well after this one.

Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.