A company is designing a new microservices architecture on AWS. Each microservice must be independently deployable and scalable. The company expects unpredictable traffic patterns with sudden spikes. Which combination of AWS services should be used to build a decoupled, resilient system?
Trap 1: Use Application Load Balancer, Amazon EC2 Auto Scaling, Amazon SQS,…
EC2 Auto Scaling has slower response to sudden spikes compared to serverless options.
Trap 2: Use Amazon API Gateway, AWS Lambda, Amazon Kinesis Data Streams,…
Kinesis is for streaming, not request-response; adding unnecessary complexity.
Trap 3: Use Application Load Balancer, Amazon ECS with Fargate, Amazon SQS,…
RDS may become a bottleneck under unpredictable spikes; DynamoDB is more suitable.
- A
Use Amazon API Gateway, AWS Lambda, Amazon SQS, Amazon DynamoDB, and Amazon CloudWatch.
This option provides serverless, decoupled, and scalable components ideal for unpredictable spikes.
- B
Use Application Load Balancer, Amazon EC2 Auto Scaling, Amazon SQS, and Amazon RDS.
Why wrong: EC2 Auto Scaling has slower response to sudden spikes compared to serverless options.
- C
Use Amazon API Gateway, AWS Lambda, Amazon Kinesis Data Streams, and Amazon DynamoDB.
Why wrong: Kinesis is for streaming, not request-response; adding unnecessary complexity.
- D
Use Application Load Balancer, Amazon ECS with Fargate, Amazon SQS, and Amazon RDS with read replicas.
Why wrong: RDS may become a bottleneck under unpredictable spikes; DynamoDB is more suitable.