A GIS processing fleet is packaged as containers and sees bursty CPU demand. The city wants to avoid oversized always-on EC2 fleets. Which compute approach fits?
Select an answer to reveal the explanation.
Short Explanation
Bursty map crunching likes containers that appear when the work appears—Fargate (or similar) scales the package without babysitting fat EC2 boxes 24/7. Laptop cron farms and browser GIS for city batches are not resilient production designs.
Full Explanation
Containerized workloads with variable CPU benefit from managed container platforms such as ECS on Fargate (or EKS) that scale task capacity with demand. Permanently oversized hosts, laptop execution, or shifting batch GIS to citizen browsers fail operational and scalability requirements.