In this session, we will look at 10 common use cases for AWS Lambda such as REST APIs, WebSockets, IoT and building event-driven systems. We will also touch on some of the latest platform features such as Provisioned Concurrency, EFS integration and Lambda Destinations and when and where we should use them.
30. ALB
1 LCU gives you
25 new connections per second
3000 active connections per minute
0.4 GB per hour for Lambda function targets
1000 rule evaluations per second
* averaged over an hour
31. 1 TPS, 200ms avg latency, 1KB data processing / req
API Gateway
ALB
$2.5921 x 60s x 60m x 24hr x 30days
@ $1.00 per hour
24hr x 30days @ $0.0225 per hour
+
1 x 24hr x 30days @ $0.008 per hour
$21.96
$9.0721 x 60s x 60m x 24hr x 30days
@ $3.50 per hour
REST
HTTP
32. 1,000 TPS, 200ms avg latency, 1KB data processing / req
API Gateway
ALB
$25921000 x 60s x 60m x 24hr x 30days
@ $1.00 per hour
24hr x 30days @ $0.0225 per hour
+
40 x 24hr x 30days @ $0.008 per hour
$246.6
$90721000 x 60s x 60m x 24hr x 30days
@ $3.50 per hour
REST
HTTP
33. services that pay by uptime are orders-of-magnitude
cheaper when running at scale
47. no support for broadcasts
(e.g. broadcasting to a million connected users equates to fetching 1M
items from DynamoDB and then make 1M API calls to API Gateway…)
62. AWS AppSync
scalable & multi-az out of the box
pay as you use ($4.00 per Million)
built-in caching (extra $)
63. AWS AppSync
scalable & multi-az out of the box
pay as you use ($4.00 per Million)
built-in caching (extra $)
built-in metrics through CloudWatch
built-in logging through CloudWatch Logs
64. AWS AppSync
scalable & multi-az out of the box
pay as you use ($4.00 per Million)
built-in caching (extra $)
built-in metrics through CloudWatch
built-in logging through CloudWatch Logs
no servers to manage