Design High-Performing Architectures Question

[Diogo Simoes]

I have some concerns/doubts about this one:

A new online banking platform has been re-designed to have a microservices architecture in which complex applications are decomposed into smaller, independent services. The new platform uses Kubernetes, and the application containers are optimally configured for running small, decoupled services.

The new solution should remove the need to provision and manage servers, let you specify and pay for resources per application as well as improve security through application isolation by design.

Which of the following is the MOST suitable solution to implement to launch this new platform to AWS?

The answer considered correct is “Use AWS Fargate on Amazon EKS with Service Auto Scaling to run the containerized banking platform”.

Another available option is “Use Amazon ECS to run the Kubernetes cluster on AWS Fargate”.

Problems I see with this answer and the explanation:

– “Service Auto Scaling” does not exist in K8S. It exists, however, in ECS.

– The explanation goes into “AWS Fargate is a serverless compute engine for containers that works with both Amazon Elastic Container Service (ECS) and Amazon Elastic Kubernetes Service (EKS).” but never explains why EKS is picked instead of ECS

Why would EKS be picked instead of ECS in this case?

IMO, EKS makes sense because the bank would, in theory, already have k8s expertise. But then the EKS answer throws “Service Auto Scaling” in the mix, which is quite out of place and seems wrong, as I’ve explained above.

Cheers

• This discussion was modified 2 weeks, 6 days ago by  Diogo Simoes.