WorkflowFor DevelopersSystem Design & Architecture

Scalability Review & Upgrade Plan.

When the current system is hitting limits and you need a structured plan to scale it without a full rewrite.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1950 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
scalability-review-upgrade-plan-4.md Β· 1950 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: System Design & Architecture
- Use case: Scalability Review & Upgrade Plan
- Source task:
  - My current system: {{describe_architecture}}. Current load: {{users_requests_per_second}}. Problem: {{describe_the_scaling_bottleneck}}.
  - Step 1: Diagnose: identify the top 3 architectural bottlenecks preventing scale.
  - Step 2: Solutions: for each bottleneck, propose 2 solutions with trade-offs (horizontal scaling, sharding, CQRS, read replicas, etc.).
  - Step 3: Roadmap: prioritise the solutions in implementation order with effort estimates and the expected scale gain from each.

# Goal
3-bottleneck diagnosis, 2 solutions per bottleneck with trade-offs, and a prioritised scaling roadmap with effort and impact estimates.

# Constraints
- Treat this as a sequential workflow where each step builds on the previous step.
- Keep every step clearly labeled and easy to run separately if needed.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
3-bottleneck diagnosis, 2 solutions per bottleneck with trade-offs, and a prioritised scaling roadmap with effort and impact estimates.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Rolescalability architect
{{use_case}}Your specific valuescalability review & upgrade plan
{{describe_architecture}}Describe architectureExample describe architecture
{{users_requests_per_second}}Users requests per secondUSERS
{{describe_the_scaling_bottleneck}}Describe the scaling bottleneckExample describe the scaling bottleneck

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When the current system is hitting limits and you need a structured plan to scale it without a full rewrite.

PRO TIP

Scale the bottleneck, not the whole system β€” over-scaling non-bottleneck components wastes money and adds unnecessary complexity.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’