How will the application
handle server hardware failure?
How can I control
access from my servers?
When should I decide to
scale out my servers?
When should I decide to
scale up my servers?
What size servers are
right for my budget?
How much remaining
capacity do my servers have?
Operations and management Scaling
Provisioning and utilization Availability and fault tolerance
Owning servers means dealing with ...
Key Differences Between Compute Offerings
VM Task Function
Service EC2 ECS Lambda
H/W OS Runtime
Unit of scale
AWS Lambda: Run code in response to events
FUNCTION SERVICES (ANYTHING)
Amazon S3 Amazon
AWS CloudTrail Amazon
DATA STORES ENDPOINTS
CONFIGURATION REPOSITORIES EVENT/MESSAGE SERVICES
Example event sources that trigger AWS Lambda
… and a few more with more on the way!
AWS IoT AWS Step
Using AWS Lambda
Bring your own code
• Node.js, Java, Python,
• Bring your own libraries
Simple resource model
• Select power rating from
128 MB to 1.5 GB
• CPU and network
• Synchronous or
• Integrated with other
• Use processes, threads,
/tmp, sockets normally
• AWS SDK built in
(Python and Node.js)
• Each event is a Lambda request
• Lambda scales to match the
• Don’t worry about over or under
• Pay only for what you use
Common Use Cases
• Complex web
• Packages for
• Real time
• Apps &
• Alexa Skills
• Policy engines
No servers to provision
Scales with usage
Never pay for idle Availability and fault
tolerance built in
Benefits of Lambda and Serverless Compute
AWS Lambda Pricing
• Charged by
• Request count
($0.2 per 1m requests)
($0.00001667 per GB*second)
• Buy compute time in
100 ms increments
• No minimums fees
• No per-device fees
1 million requests and 400,000
GB*second of compute every month,
• 256MB of memory
• Executed 3 million times per month
• It ran for 1 second each time
Around $6.2 per month!
• Serverless doesn’t actually mean that we have no
servers. It means that you don’t need to deal with them
anymore and focus on your business logic
• Many use cases can go Serverless computing
• Web, data processing, interactive backends, Chatbots, Alexa,
auto managing AWS resources
• Bots development on AWS is easy and agile
• Serverless ecosystem continues to grow
• Tooling, languages, and application capabilities
1. Go to console.aws.amazon.com/lambda and create your first
2. Stay up to date with AWS Lambda on the Compute blog and check
out aws.amazon.com/lambda for scenarios and customer stories.
3. See https://aws.amazon.com/serverless for reference
architectures, samples, and links to more content.
4. Send us your questions, comments, and feedback on the AWS