Serverless vs container decision in AWS - Visual Side-by-Side Comparison

Process Flow - Serverless vs container decision

Start: Need to deploy app

↓

Check app scale needs

↓

Serverless

↓

Auto scale

↓

Pay per use

↓

Deploy

This flow shows how to decide between serverless and containers based on app scale and management needs.

Execution Sample

AWS

if app_scale == 'low':
    use_serverless()
else:
    use_container()

Simple decision: use serverless for low scale apps, containers for high scale apps.

Process Table

Step	app_scale	Condition	Decision	Action
1	low	app_scale == 'low'	True	use_serverless()
2	high	app_scale == 'low'	False	use_container()
3	medium	app_scale == 'low'	False	use_container()

💡 Decision made based on app_scale value; serverless chosen for low, container otherwise.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
app_scale	undefined	low	high	medium
Decision	undefined	serverless	container	container

Key Moments - 2 Insights

Why do we choose serverless only when app_scale is low?

Because serverless automatically scales and charges per use, it is cost-effective for low or unpredictable traffic. See execution_table row 1 where condition is True.

Why containers are chosen for medium scale?

Containers give more control and can handle steady or high traffic better. In execution_table rows 2 and 3, condition is False, so container is chosen.

Visual Quiz - 3 Questions

Look at the execution_table, what decision is made when app_scale is 'high'?

A Use container

B No decision

C Use serverless

D Use both

💡 Hint

Check row 2 in execution_table where app_scale is 'high' and decision is shown.

At which step does the condition app_scale == 'low' become false?

A Step 1

B Step 2

C Step 3

D Never

💡 Hint

Look at execution_table rows 2 and 3 where condition is False.

If app_scale was 'low' at step 3, what would the decision be?

A Use container

B No decision

C Use serverless

D Use both

💡 Hint

Refer to execution_table row 1 where app_scale is 'low' and decision is serverless.

Concept Snapshot

Decision to use serverless or containers depends on app scale.
Serverless: best for low or unpredictable scale, auto scales, pay per use.
Containers: better for steady or high scale, more control, manage resources.
Simple check: if app_scale == 'low' then serverless else container.
Choose based on cost, control, and scale needs.

Full Transcript

This visual execution shows how to decide between serverless and container deployment on AWS. We start by checking the app's scale needs. If the app scale is low, we choose serverless because it automatically scales and charges only for usage, making it cost-effective. If the app scale is medium or high, we choose containers for better control and resource management. The execution table traces three steps with different app_scale values and shows the decision made at each step. Variables app_scale and Decision change accordingly. Key moments clarify why serverless suits low scale and containers suit higher scale. The quiz tests understanding of decisions at each step. The snapshot summarizes the decision logic simply.

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