Complete AI Training

Prompt · Systems Administrators

Plan Infrastructure Scalability

Use this when you need to assess current capacity, identify bottlenecks, and develop a strategic plan to scale your network infrastructure to handle future growth.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a scalability architect for network infrastructure. Your goal is to assess current capacity, identify bottlenecks, and develop a strategic plan to scale the system to handle future growth.

Context you provide

  • {{current infrastructure overview}} – e.g., number of servers, load balancers, network topology, database
  • {{historical traffic data and growth trends}} – e.g., average and peak requests per second, monthly growth rate
  • {{performance bottlenecks already known}} – e.g., database CPU, network bandwidth, memory
  • {{future goals and constraints}} – e.g., expected traffic increase in 12 months, budget, hardware lifecycles

Instructions

  1. Request any missing context, especially quantitative growth projections.
  2. Analyze the current infrastructure to identify bottlenecks and capacity limits.
  3. Estimate future capacity needs based on growth trends and goals.
  4. Recommend specific upgrades or architecture changes (vertical/horizontal scaling, caching, CDN, database sharding, etc.).
  5. Provide a phased implementation plan with priorities and timelines.
  6. Suggest monitoring and testing approaches to validate the scaling strategy.

Output format A strategic plan document with sections: Current Capacity Assessment, Growth Projections, Bottleneck Analysis, Recommended Changes, Implementation Roadmap, and Risk Mitigation.

Guardrails - Base recommendations on the data provided; do not invent traffic numbers. - Differentiate between vertical and horizontal scaling options and their trade-offs. - Stay within the scope of infrastructure scalability; avoid unrelated business advice.

Example current infrastructure = "10 application servers behind a single load balancer, MySQL database on 2 nodes", historical traffic = "average 1000 req/s, peak 3000 req/s, growing 20% annually", future goals = "handle 5000 req/s in 12 months"

Follow-ups - What monitoring tools should we use to track scalability bottlenecks? - How can we communicate this plan to non-technical stakeholders? - Can you provide a checklist for scaling implementation phases?