AWS Lambda Reviews & Product Details

It’s a serverless service that scales automatically with traffic. You pay only for what you use, and it supports multiple languages. Review collected by and hosted on G2.com.

The execution time is a bit limited; however, it looks good overall. Review collected by and hosted on G2.com.

What I like most about AWS Lambda is how it completely removes the need to manage servers. You just focus on writing code, and it takes care of everything else—scaling, patching, provisioning. It’s incredibly efficient, especially for event-driven tasks like processing S3 uploads, reacting to database changes, or triggering workflows based on user actions. It also scales automatically, so whether you’re handling one request or a thousand, it just works without you needing to plan for capacity. Plus, the pay-as-you-go model means you're only charged for the time your code actually runs, which is great for keeping costs low. I also appreciate how well Lambda integrates with the rest of the AWS ecosystem—whether it's SQS, DynamoDB, or Step Functions, it all ties together seamlessly. It’s a powerful tool for building modern, scalable, and cost-effective applications. Review collected by and hosted on G2.com.

One of the main things I dislike about AWS Lambda is the **cold start latency**, especially when using certain runtimes like Java or when functions are in a VPC. That delay, even if it's just a couple of seconds, can be noticeable in user-facing applications. Another challenge is **limited observability** out of the box—while you can plug in tools like CloudWatch or X-Ray, it often takes extra effort to get clear visibility into performance and failures. Also, **debugging and testing locally** can be tricky, especially when dealing with event sources like API Gateway or DynamoDB streams. And while the simplicity is great for small functions, managing a large number of Lambdas can get messy fast—things like versioning, environment variables, permissions, and deployment pipelines need to be tightly organized. Finally, the **timeout and memory limits** make Lambda unsuitable for certain long-running or resource-heavy workloads, so you have to design around those constraints. Review collected by and hosted on G2.com.

- I like that I can write a specific function or unit of code which is focus on performing a single task

- You only pay for the amount of time you run it and this encourages you to optimize your code in terms of time and space complexities to save money

- Simple to use and setup and execute once you get the hang of it

- Can be used to re-write the origin of your CloudFront Distribution as well and allows the static hosting using S3

- I believe that lambda is at the core of AWS services and can be helpful in accomplishing many tasks across a range of services

- It can be used to create a range of microservices too Review collected by and hosted on G2.com.

- If you do not optimize the code, you may end up paying more

- Supports limited languages in which you can write the lambda Review collected by and hosted on G2.com.

What I like best about AWS Lambda is how easy it makes running code without worrying about managing servers. I can just upload my code, set up a trigger, and Lambda automatically scales to handle anything I throw at it—whether it’s a few requests or thousands, all without me having to do any infrastructure work. It’s fast, simple, and lets me focus on building, not maintaining. Review collected by and hosted on G2.com.

One thing I dislike about AWS Lambda is that it has some limitations that can be frustrating, like the 15-minute execution time limit and occasional cold start delays, which can slow things down if your function hasn’t run in a while. There are also restrictions on memory, storage, and payload size, so it’s not great for big or long-running tasks. Plus, since Lambda is so tightly tied to AWS, moving your application elsewhere can be tricky, and debugging can sometimes be harder than in traditional setups. Review collected by and hosted on G2.com.

I like best about AWS Lambda is its serverless nature, which removes the need to manage infrastructure. I can focus purely on writing code while AWS handles scaling, availability, and maintenance. Review collected by and hosted on G2.com.

main drawbacks of AWS Lambda is the cold start latency, which can impact performance for applications that need consistent low response times, especially when functions are not invoked frequently. Review collected by and hosted on G2.com.

I’ve been using AWS Lambda for some time, and what I appreciate most is not having to deal with server management. It simply works, scaling automatically when necessary, and I only pay for the actual runtime of my code. Setting up triggers from S3 or DynamoDB is extremely convenient and saves a significant amount of deployment time. Honestly, it makes developing small applications or microservices much easier, as I can concentrate on writing code rather than handling infrastructure. Review collected by and hosted on G2.com.

Lambda has a maximum timeout of 15 minutes, which makes it unsuitable for long-running tasks. Review collected by and hosted on G2.com.

It has a great feature to run any application with ease and hassle free. Using this expanding application according to the load is very easy. Implementation of lamda fuction is easy and seamless along multiple integration. Review collected by and hosted on G2.com.

Although all features are great but as customer we have very less control on it as this is completly managed by the aws itself. Review collected by and hosted on G2.com.

I use it to develop scalable, event-driven services without the overhead of managing the infrastructure. Review collected by and hosted on G2.com.

For latency-sensitive applications cold starts are not optimal and managing permissions feels complex and difficult to handle. Review collected by and hosted on G2.com.

What I like best about AWS Lambda is how it simplifies development by removing the need to manage servers—just write the function, set the trigger, and it runs when needed. It’s incredibly easy to implement and integrates smoothly with other AWS services like S3, DynamoDB, and API Gateway, which makes building complex workflows feel intuitive. The number of features available is impressive, and I find myself using it frequently for automation and event-driven tasks. Customer support has been generally helpful, especially through documentation and forums, though direct support could be more responsive at times. Overall, Lambda strikes a great balance between ease of use, powerful functionality, and scalability. Review collected by and hosted on G2.com.

One thing I dislike about AWS Lambda is the cold start latency, especially when using certain runtimes or when functions aren't invoked frequently—it can slow down response times noticeably. Debugging can also be a bit tricky since the environment is abstracted and logs are the main way to trace issues. While integration with other AWS services is strong, it sometimes feels like you're locked into the AWS ecosystem, which can limit flexibility. The limits on execution time and memory can be restrictive for more complex workloads, and managing deployments across multiple environments can get cumbersome without additional tooling. Lastly, while customer support is available, getting timely, hands-on help often requires a premium support plan. Review collected by and hosted on G2.com.

I just give it my code, and it handles the rest.

It is fast to develop.

Most servers cost money even when they are doing nothing. Lambda is different: if your code runs for two seconds, you only pay for those two seconds. Review collected by and hosted on G2.com.

It kills the process in a short period of time, like 15 minutes, I think. Review collected by and hosted on G2.com.