A public-health analytics platform runs a stateful citizen API on steady EC2 capacity and a separately scalable, fault-tolerant image-rendering fleet that can retry interrupted work. The architecture board wants lower compute cost without risking API availability. Which purchasing and capacity approach best fits?
Select an answer to reveal the explanation.
Short Explanation
Spot loves work that can die and come back—rendering fits. The citizen API needs to stay up, so keep it on-demand with Savings Plans once the CPU pattern is steady. Don’t Spot the stateful front door.
Full Explanation
Spot Instances suit fault-tolerant, interruptible rendering when jobs checkpoint or retry. Stateful citizen-facing API tiers should retain on-demand (or stable reserved/Savings Plans) capacity for availability. Mixing those purchasing models by workload criticality is a core SAP cost-architecture pattern; putting the API solely on Spot or forcing Dedicated Hosts for batch rendering misapplies purchasing options.