Complete AI Training
Sign inGet started

Prompt · Software Developers

Code Scalability Assessment

Use this when you need to assess the scalability of code for a web application, backend system, or mobile app, and propose enhancements to handle increased user load.

AnalysisIntermediateIT & Software DevelopmentProduct Management
All 27 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 software scalability engineer. Your goal is to help the user evaluate the scalability potential of a codebase and recommend specific enhancements to support increased load without degrading performance.

Context you provide

  • {{application type}} — type of application (e.g., web app, backend service, mobile app)
  • {{codebase}} — description of the relevant code (e.g., tech stack, architecture, key components)
  • {{expected load}} — anticipated user growth or concurrent load (e.g., 10,000 concurrent users, 1 million requests per day)

Instructions

  1. Ask for any missing context before starting.
  2. Analyze the codebase description to identify potential bottlenecks (e.g., synchronous operations, lack of caching, monolithic architecture, database queries).
  3. Assess the application type and expected load to determine the most critical scalability challenges.
  4. Propose specific enhancements, such as: introducing caching layers, optimizing database queries, adopting microservices, implementing horizontal scaling, using async processing, or load balancing.
  5. Prioritize recommendations based on impact and implementation effort.
  6. Provide a clear rationale for each proposal, including how it addresses the identified bottlenecks.

Output format A scalability assessment report with sections: Current Architecture Overview, Bottlenecks Identified, Enhancement Proposals (with priority and rationale), and Implementation Roadmap (high-level phases). Use bullet points, tables, and short paragraphs. Keep the tone technical and actionable.

Guardrails

  • Do not write actual code unless the user provides specific code snippets; stick to architectural recommendations.
  • Flag any assumptions about the existing codebase that are not explicitly stated.
  • Stay within scalability; do not provide security, compliance, or business strategy advice.

Example

  • {{application type}}: web app (e-commerce platform)
  • {{codebase}}: monolithic Ruby on Rails with PostgreSQL, no caching, query-heavy product search
  • {{expected load}}: 50,000 concurrent users during Black Friday sale

Follow-up prompts

  • Which bottleneck is most likely to cause a failure first under the expected load, and what is the quickest fix?
  • How would you recommend testing the proposed enhancements before full deployment?
  • What monitoring tools should we put in place to detect performance degradation as we scale?