Scribd
Upload
16 views18 pages

AWS Lambda

Serverless is a cloud-native development model that allows developers to build applications without managing servers, as the cloud provider handles server provisioning and scaling. AWS Lambda is a serverless compute service that executes code only when needed, automatically scales, and charges based on compute time used. This architecture is ideal for applications with unpredictable demand and offloads routine management tasks to the cloud provider.

Uploaded by

Abdulhay Allooh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
16 views18 pages

AWS Lambda

Serverless is a cloud-native development model that allows developers to build applications without managing servers, as the cloud provider handles server provisioning and scaling. AWS Lambda is a serverless compute service that executes code only when needed, automatically scales, and charges based on compute time used. This architecture is ideal for applications with unpredictable demand and offloads routine management tasks to the cloud provider.

Uploaded by

Abdulhay Allooh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 18

Lambda

Serverless
• Serverless is a cloud-native development model
• Developers can build and run applications without managing
servers
• Servers are abstracted away from app development
• Cloud provider handles server provisioning, maintenance, and
scaling
Serverless ¬ Code can be packaged in containers for deployment
¬ Serverless apps automatically scale up and down based on demand
¬ Serverless offerings from public cloud providers are usually metered
on-demand
¬ Based on an event-driven execution model
¬ Idle serverless functions do not incur costs
An Overview of Serverless
Architecture
Serverless Architecture

Serverless is different from other cloud computing models

Cloud provider manages both infrastructure and app scaling

Serverless apps are deployed in containers that launch on demand

Standard IaaS model requires pre-purchased capacity

User responsible for scaling server capacity


Serverless Architecture

Cloud infrastructure remains active even when app isn't used

Serverless apps launch only when triggered by an event

Public cloud provider dynamically allocates resources for app code

User stops paying when code finishes executing

Serverless architecture provides cost and efficiency benefits


Serverless Architecture

Developers are freed from routine tasks of app scaling and


server provisioning

Management tasks like operating system, file system, security


patches, etc., are offloaded to cloud services provider

Apps can be entirely serverless or a mix of serverless and


traditional microservices components
Serverless Architecture
Under a serverless model, a cloud provider runs physical servers and dynamically
allocates their resources on behalf of users who can deploy code straight into
production
Serverless Use Cases
Serverless Use Cases

Serverless architecture is ideal for Serverless is a good fit for use cases that see
asynchronous, stateless apps that can be infrequent, unpredictable surges in demand
started instantaneously
Batch Processing

Must be ready
Batch processing
when a large
of incoming Run infrequently
batch of images
image files
arrives all at once
Common Use
¬ Incoming data streams
¬ Chat bots

Cases ¬ Scheduled tasks


¬ Business logic
¬ Back-end APIs
Common Use Cases

Web apps Business Serverless Integration across


automation websites multiple systems
What is Lambda?
Lambda
• AWS Lambda allows running code without server management
• Lambda runs code on a high-availability compute infrastructure
• Administration tasks like server maintenance and capacity provisioning are handled by Lambda
• Code needs to be supplied in one of the supported language runtimes
Lambda
• Code is organized into Lambda functions
• Functions are executed only when needed and automatically scaled
• Billing is based on the consumed compute time
• No charges when the code is not running
When to use
Lambda is an ideal compute service for
application scenarios that need to scale up
rapidly, and scale down to zero when not in
Lambda? demand
When to use Lambda?
• When using Lambda, you are only responsible for your code
• Lambda manages the compute fleet and resource allocation for your code
• No access to compute instances or customization of the operating system on provided
runtimes
• Lambda performs operational and administrative activities on your behalf
• Activities include managing capacity, monitoring, and logging of Lambda functions

You might also like