Calculating Capacity
The Capacity Canvas helps forecast API traffic patterns to ensure the platform can handle expected and peak loads. It provides critical input for scaling decisions and infrastructure planning.
Detailed guide related to APIOps Cycles phase:
API Platform ArchitectureHow to Use:
- Identify Business Transactions Driving API Traffic:
- Document the core business processes that generate API requests (e.g., user logins, data synchronization, payment processing).
- Estimate transaction frequency and expected growth rates.
- Plot Traffic Patterns:
- Use the graph to map expected traffic over time:
- X-Axis: Time intervals (e.g., 1 month, 6 months, 12 months).
- Y-Axis: Business transaction volume or API calls.
- Include regular fluctuations (e.g., daily peaks) and anticipated surges (e.g., seasonal traffic or marketing campaigns).
- Use the graph to map expected traffic over time:
- Plan for Scalability:
- Based on the traffic forecast, define infrastructure requirements:
- Compute power (e.g., scaling servers).
- Storage needs.
- Network capacity.
- Align your scaling strategy with the API’s expected lifecycle.
- Based on the traffic forecast, define infrastructure requirements:
Output:
A data-driven plan for scaling the API platform, ensuring it meets performance requirements under varying traffic loads.
How to use the Capacity -template
Back to related APIOps Cycles phase:
API Platform ArchitectureAPIOps Cycles
method for lean api development
Great APIs need skilled people and a good method, which let's you create APIs as products - fast.
APIOps Cycles method is vendor & technology-neutral.
Read the free e-book "The 8 wastes of lean in API development". Learn quick tips on how to remove the wastes using the APIOps Cycles method.
