Serverless vs container decision in AWS - Performance Comparison

Time Complexity: Serverless vs container decision

O(n)

Understanding Time Complexity

When choosing between serverless and containers, it's important to understand how the time to handle tasks grows as workload increases.

We want to see how the number of operations or API calls changes when we add more tasks.

Scenario Under Consideration

Analyze the time complexity of deploying and running tasks using serverless functions versus containers.

// Serverless example
for each event in events:
  invoke Lambda function(event)

// Container example
for each task in tasks:
  schedule task on ECS cluster

This sequence shows invoking a serverless function for each event versus scheduling tasks on a container cluster.

Identify Repeating Operations

Look at what repeats as workload grows.

• Primary operation: Invoking a Lambda function or scheduling a container task.
• How many times: Once per event or task, so it grows with the number of events/tasks.

How Execution Grows With Input

As the number of events or tasks increases, the number of function invocations or container schedules increases proportionally.

Input Size (n)	Approx. API Calls/Operations
10	10 Lambda invocations or 10 container task schedules
100	100 Lambda invocations or 100 container task schedules
1000	1000 Lambda invocations or 1000 container task schedules

Pattern observation: The number of operations grows directly with the number of tasks or events.

Final Time Complexity

Time Complexity: O(n)

This means the time or number of operations grows linearly as the number of tasks or events increases.

Common Mistake

[X] Wrong: "Serverless automatically handles all tasks instantly, so time doesn't grow with more events."

[OK] Correct: Each event still triggers a separate function call, so total operations increase with more events.

Interview Connect

Understanding how workload size affects operations helps you explain design choices clearly and shows you grasp cloud scaling basics.

Self-Check

What if we batch multiple events into a single serverless function call? How would the time complexity change?

Practice

1. Which AWS service lets you run code without managing servers, automatically scaling with demand?

easy

A. Amazon ECS

B. AWS Lambda

C. Amazon EC2

D. AWS Elastic Beanstalk

Solution

1. Step 1: Understand serverless concept

   Serverless means you don't manage servers; code runs on demand.

2. Step 2: Identify AWS service matching serverless

   AWS Lambda runs code without server management and scales automatically.

3. Final Answer:

   AWS Lambda -> Option B

4. Quick Check:

   Serverless = AWS Lambda [OK]

Hint: Serverless means no servers to manage, pick Lambda [OK]

Common Mistakes:

• Choosing EC2 which requires server management
• Confusing containers with serverless
• Picking Elastic Beanstalk which manages servers but not fully serverless

2. Which AWS service is best described by this syntax snippet for deploying a container?

aws ecs create-cluster --cluster-name myCluster

easy

A. Amazon S3 bucket creation

B. AWS Lambda function deployment

C. Amazon ECS container cluster creation

D. AWS CloudFormation stack deployment

Solution

1. Step 1: Analyze the command

   The command uses 'aws ecs create-cluster' which is for ECS clusters.

2. Step 2: Match command to service

   ECS is AWS service for managing containers in clusters.

3. Final Answer:

   Amazon ECS container cluster creation -> Option C

4. Quick Check:

   "aws ecs create-cluster" = ECS container cluster [OK]

Hint: ECS commands manage containers, Lambda uses different syntax [OK]

Common Mistakes:

• Thinking this command deploys Lambda functions
• Confusing S3 bucket commands with ECS
• Assuming CloudFormation syntax

3. You have a web app that needs to run continuously with custom OS settings. Which AWS option fits best?
Options:
A) AWS Lambda
B) AWS CloudFront
C) Amazon S3
D) Amazon ECS with Fargate

medium

A. AWS Lambda

B. AWS CloudFront

C. Amazon S3

D. Amazon ECS with Fargate

Solution

1. Step 1: Identify app requirements

   The app runs continuously and needs custom OS settings, so it needs control over environment.

2. Step 2: Match service to requirements

   AWS Lambda is event-driven and short-lived, not continuous. ECS with Fargate runs containers continuously with environment control.

3. Final Answer:

   Amazon ECS with Fargate -> Option D

4. Quick Check:

   Continuous app + custom OS = ECS Fargate [OK]

Hint: Continuous with custom OS? Choose containers (ECS) not Lambda [OK]

Common Mistakes:

• Choosing Lambda for continuous workloads
• Confusing S3 (storage) or CloudFront (CDN) as compute
• Ignoring environment control needs

4. You tried running a container on AWS Lambda but it failed. What is the likely cause?

medium

A. Lambda does not support running containers longer than 15 minutes

B. Lambda requires a Dockerfile to deploy containers

C. Lambda only supports Python code, not containers

D. Lambda cannot run containers at all

Solution

1. Step 1: Understand Lambda container support

   Lambda supports container images but has a max execution time of 15 minutes.

2. Step 2: Identify cause of failure

   If container runs longer than 15 minutes, Lambda will fail the execution.

3. Final Answer:

   Lambda does not support running containers longer than 15 minutes -> Option A

4. Quick Check:

   Lambda container max time = 15 minutes [OK]

Hint: Lambda containers have 15-minute max runtime limit [OK]

Common Mistakes:

• Thinking Lambda cannot run containers at all
• Believing Lambda only supports Python code
• Confusing Dockerfile requirement

5. Your startup wants to minimize costs and avoid managing servers for a new app with unpredictable traffic spikes. Which AWS approach is best?

hard

A. Deploy on AWS Lambda for automatic scaling and no server management

B. Use Amazon ECS with EC2 instances for full control

C. Host on Amazon EC2 with manual scaling

D. Use AWS Elastic Beanstalk with fixed server capacity

Solution

1. Step 1: Analyze startup needs

   Startup wants to minimize costs and avoid managing servers, with unpredictable traffic.

2. Step 2: Match AWS service to needs

   AWS Lambda automatically scales with traffic and requires no server management, reducing cost and effort.

3. Step 3: Compare other options

   ECS with EC2 or Elastic Beanstalk requires server management or fixed capacity, increasing cost and complexity.

4. Final Answer:

   Deploy on AWS Lambda for automatic scaling and no server management -> Option A

5. Quick Check:

   Min cost + no servers + spikes = Lambda [OK]

Hint: No servers + spikes? Pick Lambda for auto scaling [OK]

Common Mistakes:

• Choosing ECS or EC2 which need server management
• Assuming Elastic Beanstalk auto-scales without servers
• Ignoring cost and management factors