Examkin

Soru

Zorluk: OrtaServerless and Automated Scaling Architectures for Cost Efficiency

A financial brokerage platform processes a continuous, steady stream of stock market trade executions to update user portfolio balances. The system operates 24/7, handling a high and constant volume of transactions. The updates for each individual user portfolio must be processed in the exact sequence the trades occurred. The current architecture uses an AWS Lambda function triggered by an Amazon SQS standard queue to process the trade records. This configuration is experiencing high operational costs and occasional incorrect portfolio balances. Which solution will resolve these issues most cost-effectively?

  1. A
    Change the queue to an Amazon SQS FIFO queue but continue using the existing AWS Lambda function for processing.
  2. B
    Deploy the processing application on an Amazon ECS service running on AWS Fargate, but continue using the Amazon SQS standard queue.
  3. Deploy the processing application on an Amazon ECS service running on AWS Fargate, and replace the Amazon SQS standard queue with an Amazon SQS FIFO queue.Cevap
  4. D
    Configure AWS Lambda to run inside a VPC and use an Amazon Kinesis Data Stream instead of the SQS queue.

Cevap

Deploy the processing application on an Amazon ECS service running on AWS Fargate, and replace the Amazon SQS standard queue with an Amazon SQS FIFO queue.
The correct solution optimizes both cost and correctness. Utilizing Amazon SQS FIFO queues guarantees that events for each unique portfolio are processed sequentially, resolving the incorrect balances. Since the ingestion pipeline runs continuously 24/7 at a high and constant volume, hosting the consumer code in a containerized environment using Amazon ECS on AWS Fargate is significantly more cost-efficient than AWS Lambda, which incurs high costs when running continuously.

Adım Adım Çözüm

1
Analyze the workload characteristics and requirements.
Identify that the workload runs 24/7 continuously with a steady, high volume, and requires strict message ordering per user portfolio.
Understanding workload pattern (continuous vs. spiky) is key to selecting the most cost-efficient compute model, and ordering constraints dictate the messaging technology.
2
Evaluate the compute options for continuous 24/7 execution.
Determine that Amazon ECS on AWS Fargate is more cost-effective than AWS Lambda, which is optimized for short, intermittent, or event-driven tasks.
AWS Lambda charges per invocation and duration, which accumulates high costs under 100% utilization. A container running on ECS Fargate has a fixed baseline cost that is cheaper for continuous consumption.
3
Address the strict ordering requirement.
Select Amazon SQS FIFO queues instead of standard queues, using the portfolio ID as the MessageGroupId.
Standard SQS queues only provide best-effort ordering, whereas SQS FIFO guarantees first-in, first-out delivery and single-consumer processing per message group.

Anahtar Kavram

Selecting cost-effective compute (Lambda vs. ECS Fargate) based on workload execution continuity alongside queue ordering constraints.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Serverless and Automated Scaling Architectures for Cost Efficiency