1. Home
  2. Function as a Service (FaaS) Software
  3. AWS Lambda Reviews
  4. User Review of AWS Lambda
AWS Lambda Review
August 13, 2019

AWS Lambda Review

Anonymous | TrustRadius Reviewer
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
It is very easy to get started with AWS Lambda and create your first function. The user interface makes it easy to add AWS services to be inputs or outputs to the function, meaning it can be configured in many different ways for different needs. This makes it ideal for various scenarios in AWS.
I have not needed support for AWS Lambda, since it is already using Python, which has resources all over the internet. AWS blog posts have information about how to install some libraries, which is necessary for some more complex operations, but this is available online and didn't require specific customer support for.
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
AWS Lambda is best used in environments where you need to perform specific actions in response to an event happening. This reduces cost and will only be billed for the CPU time it takes to run the function. For long-running tasks, AWS Lambda is not good because of the timeouts set by the function.