An excellent choice for cloud based, serverless functions
April 19, 2018

An excellent choice for cloud based, serverless functions

Kevin Van Heusen | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with AWS Lambda

AWS Lambda is a great way to perform operations in the cloud without requiring a server. We have used Lambda in our engineering team to help automate AWS related tasks and do so in a way that does not require running an AWS instance. This helped us because sometimes Lambda is one of the most efficient ways to solve a problem that involves the AWS infrastructure.
  • One of the best serverless cloud based functions out there
  • Deep integration with Amazon Web Services
  • Support for a variety of programming languages
  • Deployment of Lambda functions could be a bit more intuitive
  • Amazon could provide more examples of Lambda functions to help get started
  • A Lambda based workflow can be more complex to debug because of all the different functions that may be called as a result of your workflow
  • AWS has sped up the time to implement some functionality since we could create a Lambda function to do the work quickly
  • Lambda has reduced costs for cases which would normally require a standalone server
  • Lambda has improved resiliency of some backend functions because we don't have to worry about normal redundancy of standalone servers
Microsoft's Azure functions and Lambda occupy the same functionality conceptually. Both offer serverless functions, and can perform similar operations. Azure functions are better suited for Azure based infrastructure and Lambda is better suited for an AWS based setup. Lambda includes quite a bit of functionality to seamlessly operate with AWS, whereas Azure Functions offer more seamless operability with Azure.
Lambda is great when you have specific bite-sized functionality that you can split into multiple discrete functions. It is not well suited for large functions that do quite a bit. Sometimes you are able to split those tasks down into separate Lambda functions that effectively get chained together. For the cases where you can't, it's better to go with a standard backend.