4. AWS Lambda
Lambda
• Language runtime vs. container or VM
• Functions are unit of deployment
• Java 8, Node.js or Python 2.7
• Linux containers + packing algorithm
• Scaling handling for you
• Stateless – permanent storage is
elsewhere
• Pay per request
5. Getting email in
SES
(Simple Email Service)
Lambda SNS
(Simple Notification Service)
To: i.am.using@gcscc.site
Subject: nodejs aws-lambda
12. What I liked
• Low costs
• Very nearly free and will be even with thousands of users
• Clean architecture
• Forced to have independent functions that do one thing
• Hugely powerful and flexible toolkit
• Feels productive as a developer
• ~1 feature per hour (40 hours total)
13. What I didn’t like
• Tools are still emerging
• node-lambda used for local execution, testing and
deployment
• Can see managing many functions and will get tricky
• Setting up plumbing like SNS events and permissions not
automated (for me)
• A slight delay in cold start of Node.js functions but better
than Java
• Error handling needs a bit of thought
14. Future plans
• Cloud Formation for Lambda
• API Caching (very small $ cost)
• Tuning (turn up the dial)
• Editing web frontend with login and API authentication
• I am optimistic Lambda will become production ready