The requirements include:
Scalability: The solution must scale as video files are uploaded.
Long-running tasks: Processing tasks can take up to 30 minutes. AWS Lambda has a maximum execution time of 15 minutes, which rules out options that involve Lambda performing all the processing.
Serverless and event-driven architecture: Ensures cost-effectiveness and high availability.
Analysis of Options:
Option A:
AWS Lambda has a 15-minute timeout, which cannot support tasks that take up to 30 minutes.
EventBridge Scheduler is unnecessary for monitoring files when native event notifications are available.Not a valid choice.
Option B:
AWS Step Functions and AWS Fargate can handle long-running processes, but Amazon EFS is not the ideal storage for uploaded video files in a serverless architecture.
Processing tasks triggered by EFS events are not a common pattern and may introduce complexities.Not the best practice.
Option C:
Amazon S3 is used for storing uploaded files, which integrates natively with event-driven services like EventBridge and Step Functions.
Amazon S3 event notifications trigger a Step Functions workflow, which can orchestrate Fargate tasks to process large video files, meeting the scalability and execution time requirements.Correct choice.
Option D:
Similar to Option A, AWS Lambda cannot handle long-running processes due to its 15-minute timeout.
Invoking Lambda for processing directly is not feasible for tasks that take up to 30 minutes.Not a valid choice.
AWS References:
Amazon S3 Event Notifications:AWS Documentation - S3 Event Notifications
AWS Step Functions:AWS Documentation - Step Functions
AWS Fargate:AWS Documentation - Fargate
Comparison of Storage Services:AWS Storage Options
By leveragingAmazon S3,Step Functions, andFargate, this solution provides a scalable, efficient, and serverless approach to handling video processing tasks.
Submit