Serverless vs container decision in AWS - Quick Revision & Key Differences

Recall & Review

beginner

What is a serverless architecture?

Serverless means you write code without managing servers. The cloud provider runs your code only when needed and scales automatically.

beginner

What is a container in cloud computing?

A container packages your app and its environment so it runs the same anywhere. You manage the container but it isolates your app from the system.

intermediate

When should you choose serverless over containers?

Choose serverless if you want to avoid managing servers, have unpredictable traffic, and need fast scaling with simple code.

intermediate

What are benefits of using containers instead of serverless?

Containers give you more control, can run complex apps, support many languages, and work well for long-running tasks.

intermediate

Name a key limitation of serverless architectures.

Serverless functions often have time limits and less control over the environment, which can be a problem for long or complex processes.

Which option best describes serverless computing?

A Code runs only when triggered and scales automatically

B You manage servers and scale manually

C You package apps with their environment

D You run virtual machines on your laptop

Serverless means your code runs only when needed and the cloud provider handles scaling automatically.

What is a main advantage of containers over serverless?

A More control over app environment and longer running processes

B Automatic scaling without limits

C Code runs only on demand

D No need to manage any infrastructure

Containers let you control the environment and run apps that need longer or complex processing.

Which scenario is best suited for serverless?

A A desktop application

B A long-running data processing job

C A legacy app needing specific OS settings

D An app with unpredictable traffic spikes

Serverless is great for apps with unpredictable traffic because it scales automatically.

What is a common limitation of serverless functions?

A They require manual scaling

B They cannot run in the cloud

C They have execution time limits

D They need a container to run

Serverless functions often have limits on how long they can run.

Which AWS service is an example of serverless computing?

A Amazon EC2

B AWS Lambda

C Amazon ECS

D Amazon S3

AWS Lambda runs code without managing servers, making it a serverless service.

Explain the main differences between serverless and container architectures.

Think about how much control you have and how scaling works.

Describe situations where choosing serverless is better than containers and vice versa.

Consider app complexity and traffic patterns.

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