A software-as-a-service (SaaS) startup is launching a new application on AWS. The workload is expected to be highly variable, with unpredictable traffic spikes throughout the day. The startup's Chief Financial Officer (CFO) wants to minimize up-front infrastructure costs and ensure that the company only pays for the compute resources it actually consumes. Which of the following strategies aligns with AWS cloud economics to meet the CFO's requirements?
- Deploying the application using an elastic architecture that automatically scales resources in response to demand, converting fixed capital expenses (CapEx) into variable operating expenses (OpEx).Answer
- BPre-purchasing a fixed capacity of dedicated physical servers located in AWS data centers to establish a long-term capital expense (CapEx), which eliminates monthly variable bills.
- CConfiguring a static, over-provisioned cluster of On-Demand instances to guarantee performance during peak hours, representing a capital expense (CapEx) that depreciates over time.
- DDeploying the database tier entirely on Spot Instances to ensure a guaranteed, low-cost baseline resource pool that is immune to unexpected terminations.
Answer
Deploying the application using an elastic architecture that automatically scales resources in response to demand, converting fixed capital expenses (CapEx) into variable operating expenses (OpEx).
The strategy of deploying an elastic architecture that scales dynamically based on real-time demand allows the startup to pay only for the resources they consume. This represents a shift from capital expenses (CapEx) to variable operating expenses (OpEx), which is a key concept of cloud economics.
Step-by-Step Solution
Key Concept
Shifting capital expenses (CapEx) to operating expenses (OpEx) through elasticity