Several municipal microservices require Kubernetes APIs and custom controllers, while a simple batch job only needs containers without Kubernetes. How should orchestration be chosen?
Select an answer to reveal the explanation.
Short Explanation
Reach for EKS when you truly need the Kubernetes toolbox; for a plain box of containers, ECS/Fargate is the lighter city work van. Putting every chore on full Kubernetes—or ditching orchestrators—is overkill or underkill.
Full Explanation
Amazon EKS is appropriate when workloads need the Kubernetes API and ecosystem. Simpler container workloads often fit Amazon ECS on Fargate with less operational depth. Avoid defaulting all work to EKS, and avoid abandoning managed orchestration for production municipal services that need scaling and placement.