Skip to main content
TrustRadius
AWS Lambda

AWS Lambda

Overview

What is AWS Lambda?

AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to…

Read more
Recent Reviews

AWS Lambda for developers

9 out of 10
May 12, 2021
AWS Lambda serves various purpose accross teams
1. We mainly use AWS Lambda when we have very short time to productionise code and have …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing

128 MB

$0.0000000021

Cloud
Per 1 ms

1024 MB

$0.0000000167

Cloud
Per 1 ms

10240 MB

$0.0000001667

Cloud
Per 1 ms

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Demos

AWS Lambda | What is AWS Lambda | AWS Lambda Tutorial for Beginners | Intellipaat

YouTube
Return to navigation

Product Details

What is AWS Lambda?

AWS Lambda is a serverless computing platform that lets developers run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes care of requirements to run and scale code with high availability. Users pay only for the compute time they consume—there is no charge when their code is not running.

Developers uploading to Lambda don’t have to deal with their code’s environment. It’s a “serverless” service which lets outside code or events invoke functions. Lambda doesn’t store data, but it allows access to other services which do. Users can set up their code to automatically trigger from other AWS services or call it directly from any web or mobile app.

AWS Lambda Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.

Reviewers rate Usability highest, with a score of 9.

The most common users of AWS Lambda are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(353)

Attribute Ratings

Reviews

(1-25 of 45)
Companies can't remove reviews or game the system. Here's why
Nikhil Singh | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • Image compression on the go
  • Supports multiple programming language which can trigger lambda using API
  • Event driven
  • Platform as service, don't need to configure underlying hardware or operating system
  • Can handle higher number of events triggering, easily scalable.
  • Cost efficient
  • Environment is something which we can't control. It can be disadvantage at some point of time.
  • Time limit for function to execute, 3 sec as default upto 15 minutes maximum. Need to a lot of time to making function more efficient to execute in given time frame.
  • If function code file is above 5mb, lambda's ide doesn't support editing on go. You need to upload another zip file with newly updated code. It's quite frustrating.
Score 9 out of 10
Vetted Review
Verified User
  • Speed processing
  • Computing concurrency
  • service to service communication
  • In Lambda if a version of the language is deprecated then it should have provide an upload or modified function.
  • It has a limit of 262 mb folder can be uploaded in AWS Lambda.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Broad support for different language runtimes: Python, Node.js, C#, Java, Golang, Powershell, Ruby
  • Save money on compute resources by paying by request volume and memory used/time
  • Integrates terrifically with a number of other AWS resources
  • Cold start--you have to account for the runtime environment being spun up every time; for a heavy operation, that can increase runtime duration and, in turn, cost
  • You have to consider networking, which is also true of other compute resources, technically
June 03, 2021

Power of lambda

Akash Singla | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • Execute small tasks quickly.
  • Monitoring can be easy.
  • Integration with s3 and SNS is a boon.
  • Trigger quickly and easily based on events.
  • Deployment via cloud formation.
  • Importing libraries.
  • Execution time could be longer.
Erlon Sousa Pinheiro | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Triggers from state changes on other AWS technologies.
  • Automate process when someone interacts with AWS S3.
  • Create functions to keep compliance aspects.
  • AWS needs to increase timeout limits for Lambda functions.
  • More templates would be welcome.
  • A better and cheaper charge policy.
Score 9 out of 10
Vetted Review
Verified User
  • Scalable
  • Less Infra headaches
  • Just write code and don’t worry about devops
  • Less plugins
  • No integration with springboot
  • Need to provide all library and no management
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Serverless compute lets you run code without provisioning and managing
  • It is helpful to reduce costs and administrative loads for web development or mobile apps
  • Easy to manage the compute resources on AWS
  • Better integration with containers
  • API Runtime should be improved with support and integration for other program languages
  • Improves documentation in part of security and network port usage
  • Limits programmers to 1,000 concurrent executions
Sai Sreenivas Addepalli | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • Serverless Framework. Easy to develop and test in local environment
  • Easy to detect issues. As it does not interlink to any other lambda.
  • There are shared layers in Lambda that can provide common code to be shared between Lambda. Helps in Avoiding the same code to be written multiple times.
  • Difficult to identify all permission issues at once. It would be easier if we can get a list of all permissions which are required to further proceed.
  • Lambda output to trigger more Services. Currently, it supports only 2-3 Services.
  • It would be great if AWS can handle the Lambda cold starts internally.
Michael Jenkins | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
  • Lambda provides multiple methods for triggering functions, this includes AWS resources and services and external triggers like APIs and CLI calls.
  • The compute provided my Lambda is largely hands off for operations teams. Once the function is deployed, the management overhead is minimal since there are no servers to maintain.
  • Lambda's pricing can be very cost effective given that users are only charged for the time the function runs and associated costs like network or storage if those are used. A function that executes quickly and is not called often can cost next to nothing.
  • Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
  • For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
  • Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
  • Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • Flexible. You can use it with many programming languages.
  • Easy. It's all configurable and as soon as you understand how it works it becomes very easy to maintain.
  • The integration with other AWS tools helps a lot the automation of tasks.
  • In the beginning, I think the documentation is not very informative so you have to look at user examples online.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • AWS Lambda is a welcoming platform, supporting several languages, including Java, Go, PowerShell, Node.js, C#, Python, and Ruby. And if you need to deploy a Lambda function in another language, AWS offers a Runtime API for integration.
  • We really appreciate how AWS Lambda is always-on for our functions, with only a brief "cold-start" waiting period the first time a function is called after being dormant.
  • In addition to only generating costs when it's actually being used, AWS Lambda really puts the "serverless" in serverless architecture, offering turnkey scaleability and high availability for our code with zero effort on our part.
  • Putting a significant portion of your codebase into AWS Lambda and taking advantage of the high level of integration with other AWS services comes with the risk of vendor lock-in.
  • While the AWS Lambda environment is "not your problem," it's also not at your disposal to extend or modify, nor does it preserve state between function executions.
  • AWS Lambda functions are subject to strict time limitations, and will be aborted if they exceed five minutes of execution time. This can be a problem for some longer-running tasks that are otherwise well-suited to serverless delivery.
October 30, 2019

AWS Lambda Review

Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • Lambda functions are best in our use case because they are serverless and you could schedule AWS Cloud watch events to run periodically.
  • Less expensive.
  • Fast execution.
  • Learning curve, it was a little bit challenging to start with, especially NodeJS runtime functions.
  • Easy alerting mechanism upon failed invocations.
  • Troubleshooting errors. We can write logs inside the function, however, if we have the ability inside the Lambda function where you raise a type of error, it can create an alert automatically, it would be great.
Jesse Bickel, MS - PMP | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • AWS Lambda is a great compute engine that allows you to run and execute your computation code without the need of maintaining servers and the overhead that comes with that.
  • We all can use our favorite programming language to develop the functions.
  • AWS Lambda is the fastest server setup on the market.
  • The relationship with S3 Triggers leaves a lot of room for improvement.
  • The solution community forums leave a lot to be desired.
  • The AWS Lambda UI experience could aid an overhaul. It's not unusable but not a great reflection of how great the service product is.
Jacob Biguvu | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • I have used the AWS Lambda for moving the RDS snapshots from cross-region like East to West and West to East. We used it as part of our DR solution. AWS Lambda is the service provided by AWS, and it makes it easy to manage the AWS resources.
  • I have used AWS Lambda for running a cleanup code against the database at scheduled times. I use Python as the coding language. AWS Lambda is the service provided by AWS, which makes easy to manage the AWS resources.
  • We can use AWS lambda function for serverless architecture.
  • We can use AWS Lambda for managing Micro-service architecture.
  • AWS Lambda has not worked in an efficient way for running long-lived applications, especially on serverless architecture.
  • AWS Lambda provides a zip deployment method, but there is a limit on size, like 500MB.
  • AWS Lambda has a significant issue with "Cold Start." It takes some time for it to handle the first request -- there, we see a real problem.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Reliable for low workloads.
  • It's an easy entry point for development.
  • Quick speed to market.
  • It would be good to have more distribution about upgrades or changes to the platform.
  • A little more documentation on the nuances of the offered supported languages.
  • A little more portability of some of the code once you've developed it from other cloud platforms.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
  • It automatically scales up your functions when demand is high.
  • It allows developers to focus only on business logic,
  • It is very cost-effective, since you're not paying for idle server time.
  • There is a lot to configure, as is the case with most of AWS's offerings. I wish it were easier to set up API Gateway with Lambda responders.
  • The default logging destination (CloudWatch) leaves much to be desired, and we opted for an external logging tool (Splunk) instead.
  • Cold starts are a persistent problem which can be mitigated with a simple cron job but would ideally be handled by the platform.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • Reliability - Lambdas just work. They do their job and quite well. I've never had any hiccups with them as a unit of hardware.
  • Scalability - This automatic scaling and availability are amazing. It's like having a fleet of servers at the ready but only when needed. And at a fraction of the cost.
  • Price - AWS gives you a generous helping of free invocations every month, and even after that, it's still cheap compared to an always-on solution.
  • The UI and Developer experience is not so great. IF you use an abstraction like Serverless Application Model (SAM), things get pretty easy, but it's still AWS UI/DX you're working with after that (which is to say, not their strength).
  • Documentation is always a mixed bag. Sometimes it's just easier to google your specific problem and see how others have solved it. This can be much faster than trying to find an example that may or may not be there in the documentation (which oftentimes has multiple versions and revisions).
August 13, 2019

AWS Lambda Review

Score 8 out of 10
Vetted Review
Verified User
Incentivized
  • 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
Richard Rout | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
  • Runs "functions" in the cloud. Pretty simple really
  • Always having the latest version available
  • Not having to worry about infrastructure
  • Anything too complex is not a great solution
  • Can take a little while to spin up if inactive for a while
  • Can be easy to misuse or abuse.
Return to navigation