Linux-based municipal microservices are being sized for a new ECS/EKS deployment. Performance tests pass on arm64 builds. Which compute choice best balances cost and performance?
Select an answer to reveal the explanation.
Short Explanation
If the containers already speak arm and the stopwatch is happy, Graviton is usually the cheaper horse. Giant x86 “just because” is how quiet services fund someone else’s yacht.
Full Explanation
AWS Graviton instances often deliver better price-performance for compatible Linux container workloads. Architects should validate arm64 images and SLAs, then select Graviton-backed fleets when metrics allow. Habit-based x86-only mandates or exotic non-target platforms ignore Task 2.6 cost-effective compute selection.