Load Modeling

Purpose

Model application load patterns and plan capacity to handle current and projected traffic. Produces a load model with growth projections, scaling trigger definitions, a benchmark plan for critical paths, and cost-at-scale estimates.

Scope Constraints

• Reads: Traffic logs, APM dashboards, infrastructure metrics, billing data, SLA documents, architecture diagrams.
• Cannot: Profile rendering performance or measure Core Web Vitals (use performance-audit). Cannot design cache hierarchies or TTL policies (use caching-strategy). Cannot provision or deploy infrastructure changes.

Inputs

• Current traffic data (requests/sec, concurrent users, peak vs average)
• Application architecture (services, databases, queues, external dependencies)
• Growth projections or business targets (user growth rate, launch events, seasonal spikes)
• Current infrastructure (instance types, database tier, CDN, serverless limits)
• SLA requirements (uptime target, max acceptable latency, error rate budget)