AWS Lambda Review
August 13, 2019
AWS Lambda Review
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with AWS Lambda
AWS Lambda is currently being used to respond to events generated within our AWS infrastructure (instances terminated/created) to perform specific actions. Because AWS Lambda is not constantly running, and only in response to events, we're able to save money by only paying for the amount of CPU resources needed when functions are run.
- Cost Savings
- AWS integration
- Python and Go support
- Need to rely on 3rd party tools for complex deployments
- Precompiled Python dependencies sometimes won't work
- Inability to share test events with other users
- Reduced cost
- Customized functions in response to events
- Hooks into other AWS services
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions