compute capacity
How much work a system can handle at once, measured in things such as servers, processors, memory or requests per second.
In more detail
In the cloud capacity is decided when you use it rather than when you buy it. A wrong guess becomes a settings change instead of a write-off. Capacity still has limits: quotas, instance sizes and the slowest dependency in the request path.
Related terms
- capacity planning — Estimating how much computing capacity a system will need and when, so it is there before the load arrives.
- elasticity — The ability of a system to grow and shrink its capacity automatically, in minutes, as demand changes.
- service quota — A limit a cloud provider sets on how much of a resource one account may use, such as how many processors or networks per region.
Taught in
- Capital to Operating Expenditure — Cloud Infrastructure & Hyperscaler Architecture
- Elasticity and Scale — Cloud Infrastructure & Hyperscaler Architecture
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- Policy Simulation and Dry Runs — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Compute Cloud (EC2) — Cloud Infrastructure & Hyperscaler Architecture
- Containers on AWS (ECS and EKS) — Cloud Infrastructure & Hyperscaler Architecture
- Comparing Compute Options — Cloud Infrastructure & Hyperscaler Architecture
- Auto Scaling Groups — Cloud Infrastructure & Hyperscaler Architecture
- Elastic Block Store (EBS) — Cloud Infrastructure & Hyperscaler Architecture
- Managed Relational Databases (RDS) — Cloud Infrastructure & Hyperscaler Architecture
- NoSQL and DynamoDB — Cloud Infrastructure & Hyperscaler Architecture