A city media desk runs containerized image-resizers that sit idle most nights and must not pay for idle capacity. Which approach best meets scale-to-zero for intermittent work?
Select an answer to reveal the explanation.
Short Explanation
Nighttime resizers should clock out like seasonal park staff—Fargate or Lambda (and ECS patterns that scale to zero) only work when there’s a queue. Ten always-on boxes or a forever Reserved Instance leave the lights on for nobody.
Full Explanation
Intermittent batch work benefits from serverless or container platforms that can scale to zero—Lambda, Fargate, or ECS services configured to allow zero running tasks—so idle periods incur little or no compute cost. Always-on EC2 fleets and immovable reserved capacity conflict with scale-to-zero goals.