A startup is deploying a data ingestion application that must run continuously 24 hours a day, 7 days a week, to consume a steady stream of updates from an external API. The processing load is constant and predictable. The startup wants to minimize compute costs for running this worker.
Which compute option is the MOST cost-effective solution for this workload?
- AAn AWS Lambda function invoked every minute by an Amazon EventBridge scheduled rule.
- Amazon ECS tasks on AWS Fargate with a Compute Savings Plan.Answer
- CAn AWS Lambda function configured with Provisioned Concurrency to keep the execution environment active.
- DAn AWS Lambda function triggered by an Amazon SQS standard queue to process messages individually.
Answer
Amazon ECS tasks on AWS Fargate with a Compute Savings Plan
Running a continuous, predictable 24/7 worker in Amazon ECS on AWS Fargate is the most cost-effective option because it provides a consistent, lower hourly rate for compute capacity, which can be further optimized with a Compute Savings Plan. In contrast, serverless functions like AWS Lambda are designed for ephemeral, event-driven tasks and charge a premium for invocation and execution time when run continuously.
Step-by-Step Solution
Key Concept
Matching workload patterns (continuous vs. ephemeral) to the correct compute billing model for cost optimization
Estimated Time:45s