This document provides information on serverless computing platforms from Azure, AWS, and Google. It outlines the supported programming languages and runtimes for each platform's functions as well as common event sources that can trigger function execution, such as S3 buckets, queues, and HTTP requests. It also lists serverless database options and notes that serverless computing allows for automatic scaling of resources and reduced management overhead compared to traditional reserved servers.

1. SERVERLESS
COMPUTING

2. CONTENTS
• Serverless providers
• Serverless runtimes
• Serverless databases
• Advantages and Disadvantages

3. SERVERLESS
PROVIDERS
• AZURE
• AMAZON (AWS)
• GOOGLE

4. SERVERLESS
RUNTIMES
AZURE Function
Language Runtime
C#, F# .NET Framework 4.7 and .NET Core 2.2,
Preview (.NET Core 3.x)
Java Java 8
Python Python 3.7.x
JavaScript,
TypeScript
Node 8 & 10
PowerShell 6
Experimental: Bash, Batch, PHP

5. SERVERLESS
RUNTIMES
AWS Lambda
Language Runtime
C# .NET Core 2.1
Java Java 8, 11
Python Python 2.7.x, 3.6.x, 3.7.x, 3.8.x
JavaScript Node 8 , 10, 12
Go go1.x
Ruby Ruby 2.5

6. SERVERLESS
RUNTIMES
Google Functions
Language Runtime
Python Python 3.7.x
JavaScript Node 8 , 10,
Go go1.x

7. SUPPORTED
EVENT SOURCES
AZURE Function
Sources
Queue A new queue message arrives which runs a function to
write to another queue.
Timer A scheduled job reads Blob Storage contents and
creates a new Cosmos DB document.
Event Grid The Event Grid is used to read an image from Blob
Storage and a document from Cosmos DB to send an
email.
HTTP A webhook that uses Microsoft Graph to update an
Excel sheet.
Supported bindings
Blob storage, Cosmos DB, Event Grid, Event Hubs, HTTP
& webhooks, IoT Hub, Microsoft Graph, Excel tables,
Microsoft Graph, OneDrive files, Microsoft Graph,
Outlook email, Microsoft Graph, events, Microsoft Graph,
Auth tokens, Mobile Apps, Notification Hub, Queue
storage, SendGrid, Service Bus, SignalR, Table storage,
Timer, Twilio

8. SUPPORTED
EVENT SOURCES
AWS Lambda
Sources
S3 events occur when someone (or something) modifies the
content of an S3 bucket.
DynamoDB
events
react to data modifications in DynamoDB tables.
API Gateway
event
Using API Gateway with Lambda is cool because you
can dynamically respond to HTTP requests with code
running on Lambda.
Amazon Alexa Lambda could be used to build new skills for AWS
voice-assistants.
CloudWatch Lambda can be used to monitor logs published on a
CloudWatch Log stream or to respond to certain metric
thresholds produced by CloudWatch Metrics.
SNS Lambda can get invoked when a message is published
to an SNS topic.
Code Commit CodeCommit can invoke a Lambda function upon
certain events in a repository, such as the creation of a
code branch.Supported bindings
Elastic Load Balancing, Cognito, Lex, Alexa, API Gateway, CloudFront,
Kinesis Data Firehose, Storage Service, Notification Service, Email
Service, CloudFormation, CloudWatch Logs and Events, Kinesis, SQS,

9. SUPPORTED
EVENT SOURCES
Google Functions
Sources
Cloud Pub/Sub You can invoke Cloud Functions in response to
messages published to Cloud Pub/Sub topics. Cloud
Pub/Sub is a globally distributed message bus that
automatically scales as you need it and provides a
foundation for building your own robust, global
services.
Cloud Storage You can invoke Cloud Functions in response to change
notifications from Cloud Storage such as object
addition (create), update (modify), or deletion.
Cloud Storage You can invoke Cloud Functions in response to change
notifications from Cloud Storage such as object
addition (create), update (modify), or deletion.
HTTP You can invoke Cloud Functions directly over HTTP(S).
Each function is given a dedicated domain and a
dynamically generated SSL/TLS certificate for secure
communication. Function execution result is returned in
response to an HTTP request.
Stackdriver
Logging
You can invoke Cloud Functions in response to log
changes in Stackdriver Logging. Stackdriver Logging
allows you to
store, search, analyze, monitor, and alert on log data

10. SERVERLESS
DATABASES
PROVIDERS
AZURE SQL Database, Cosmos DB, Table Storage
AWS Aurora, DynamoDB
GOOLE Firebase, BigQuery

11. SERVERLESS COST
CALCULATOR
Number of Executions: 100
Estimated Execution Time (ms): 10 000 000 (~166 minutes)
Memory: 512 mb
Vendor Compute Cost
AWS Lambda $1.67
Azure Functions $1.60
Google Cloud
Functions
$6.25serverlesscalc.com

12. RESERVED
Agent
Job
1
Job
2
Job
3
• Fixed CPU
• Fixed RAM

13. SERVERLESS
• On-demand CPU
• On-demand RAM

14. MICRO-PRICING

15. EASE OF SCALE
(UP & DOWN)

16. MANAGE LESS