2. Agenda
• Overview of AWS Lambda
• How it works?
• Lambda benefits
• Core Components
• Lambda Functions
• Use cases
• Resources
3. Overview
• A compute service with features:
• Server less Compute:
• lets you run code without provisioning or managing servers, just build and run
• Zero Maintenance:
• You don’t have to think about servers, over/under capacity, deployment, scaling, OS type, patch and
maintenance, matrics and logs
• Pay per use:
• executes your code only when needed and pay only for the compute time you consume - there is no
charge when your code is not running
• you pay only for the requests served and the compute time required to run your code.
• Bring your own code:
• supports code written in Node.js (JavaScript), Python, Java (Java 8 compatible), and C# (.NET Core)
4. Overview
• A compute service with features:
• Built-in Fault tolerance and auto-scaling
• is designed to use replication and redundancy to provide high availability and there are no
maintenance windows or scheduled downtimes for either.
• Security
• runs your code within a VPC by default. You can optionally also configure AWS Lambda to access
resources behind your own VPC, allowing you to leverage custom security groups and network
access control lists
• stores code in S3 and encrypts it
• Flexible resource model
• You choose the amount of memory you want to allocate to your functions and AWS Lambda
allocates proportional CPU power, network bandwidth, and disk I/O.
6. Benefits of using Lambda
• No Servers to Manage
• AWS Lambda automatically runs your code without requiring you to provision or
manage servers. Just write the code and upload it to Lambda.
• Continuous Scaling
• AWS Lambda automatically scales your application by running code in response to
each trigger. Your code runs in parallel and processes each trigger individually, scaling
precisely with the size of the workload.
• Sub-second Metering
• With AWS Lambda, you are charged for every 100ms your code executes and the
number of times your code is triggered. You don't pay anything when your code isn't
running.
7. Core Components
• There are two primary and core components of Lambda:
• Event Resource:
• An event source is the AWS service or custom application that publishes events
• Lambda Function:
• Lambda function is the custom code that processes the events
8. Lambda Function
• The code you run on AWS Lambda is called a “Lambda function.”
• After you create your Lambda function it is always ready to run as soon as
it is triggered
• Each function includes your code as well as some associated configuration
information, including the function name and resource requirements
• no affinity to the underlying infrastructure, so that Lambda can rapidly
launch as many copies of the function as needed to scale to the rate of
incoming events.
9. Use Cases
• Real Time File Processing
• use Amazon S3 to trigger AWS Lambda to process data immediately after an
upload
10. Resources
• Web Book
• https://docs.aws.amazon.com/lambda/latest/dg/lambda-dg.pdf
• FAQs
• https://aws.amazon.com/lambda/faqs/
• Videos:
• https://youtu.be/eOBq__h4OJ4
• https://www.youtube.com/watch?v=XZggsCITQdY
• https://www.youtube.com/watch?v=V10n9Uahk_M