CloudGuild · Blog · Cheat sheets · Lessons · Certifications
Optimizing Costs in Microservices: SAA-C03 Exam Walkthrough
Explore a key AWS exam question on optimizing costs in microservices. Understand the right choice and why others fall short.
Optimizing costs while maintaining performance in a microservices architecture is a common challenge. Many candidates stumble here, confused by the various AWS services that offer scalability and cost efficiency.
The question
A company is hosting a microservices architecture on AWS and wants to optimize costs while maintaining performance. Which service should they consider to reduce the operational overhead while ensuring scalability?
- A. Amazon ECS with EC2 launch type
- B. Amazon EKS with managed nodes
- C. AWS Fargate with Amazon ECS
- D. AWS Batch with EC2 Spot Instances
Think before you scroll
Consider which services allow for container management without the need for infrastructure oversight. Focus on operational overhead and scalability in a microservices context.
The answer
The correct option is C. AWS Fargate with Amazon ECS. Fargate allows you to run containers without managing the underlying infrastructure, reducing operational overhead and optimizing costs while still providing the scalability needed for microservices.
Why the other options lose
A. Amazon ECS with EC2 launch type: This option requires managing EC2 instances, which increases operational overhead. While it can scale, it does not reduce the management burden as effectively as Fargate.
B. Amazon EKS with managed nodes: EKS introduces additional complexity with Kubernetes management. It may provide scalability, but it is not the best option for optimizing costs and reducing operational overhead in a microservices architecture.
D. AWS Batch with EC2 Spot Instances: AWS Batch is designed for batch processing jobs, not for running microservices. This makes it unsuitable for the requirement of maintaining performance in a microservices architecture.
The concept behind it
The key principle is choosing a service that abstracts infrastructure management while supporting scalability. Fargate efficiently runs containers without the need to provision or manage servers, making it ideal for microservices aiming for cost optimization.
Exam trap to remember
Always prioritize services that minimize infrastructure management when optimizing for costs in a microservices architecture.