This presentation covers practical implementation of Lambda with different patterns. It also explains how to achieve continuous deployment using lambda.

1. Lambda Architecture
In Practice

2. What ?
A construct in functional programming
language to denote an anonymous
Function definition that is not bound to an
identifier

3. Ecosystem
• Dynamo
• SQS
• CloudWatch
• Serverless
• Lambada
• Chalice
• Java
• NodeJS
• Python
• AWS Lambda
• Cloud Functions
• Azure Functions
• Openwhisk
Providers Languages
Integrations
Framework
s

4. Why ?
- Event-Driven
- Elasticity
- Unpredictable
Bursty Traffic
- Lightweight Jobs
- Continuous
- Complex SOA
- Constant traffic
- Persistent
connection

5. Architecture Patterns
Monolith NanoService Hybrid
 Easy code-share
 More CPU time
 Always warm
 Difficult code-share
 Less CPU time
 Nano deployments
 Easy code-share
 Micro Deployments
 Reasonably warm

6. Framework extension
Spring
+
Jersey
Jetty
Proxy
1
3
2
4
Lambda EnvironmentAPI gateway
Conventional app deployment in Lambda

7. Scheduling & Triggers
Health Checks
Scheduled Jobs
Scheduled Warm-up
Triggers
Cloudwatch-Event
SQS
API Gateway

8. Continuous Delivery
• Plugin creates a shaded jar
• Upload to S3
• Lambda updates with latest code
• API gateway deployment

9. Limitation
Max response time = 300 sec
No persistent connection
Event payload size = 128K
Deployment size = 50 MB ( 250 MB uncompressed )
Max concurrent executions = 100
Concurrency = Events rate * Avg execution time

10. Questions ?