AWS Lambda Reviews & Product Details

What I like most about Lambda is how quickly I can run my code without needing to spin up EC2 instances. Review collected by and hosted on G2.com.

For someone like me who’s still learning, the setup isn’t the most intuitive at first, but overall I think it’s a great, affordable option. Review collected by and hosted on G2.com.

You can simply write your code and deploy it, as testing is straightforward. It's easy to connect to any runtime, and you can even trigger Lambda functions using SNS and EventBridge rules without much hassle. There's no need to manage a server—just attach an API Gateway, and you're set. Review collected by and hosted on G2.com.

What I dislike most is the cold start issue. In many of our applications, it leads to slow performance and occasionally causes errors when there are concurrent invocations. Review collected by and hosted on G2.com.

I like AWS Lambda for its serverless capability and the fact that it's easy to maintain. It's great that we don't have to worry about the server when there's a large volume on the application. Using AWS Lambda helps us scale as per demand or load on the application, which is beneficial in reducing pricing. Review collected by and hosted on G2.com.

They can improve their UI for ease. Review collected by and hosted on G2.com.

There’s no need to manage the servers at all, so I can focus on the code and the logic instead. Review collected by and hosted on G2.com.

Debugging is a pain because there’s no direct access to the server, so I can only rely on logs. Also, sometimes functions take a while to start after being idle. Review collected by and hosted on G2.com.

What stands out most about AWS Lambda is how it removes almost all the operational overhead from running code. Review collected by and hosted on G2.com.

AWS Lambda is powerful, but it definitely has some rough edges. The same things that make it convenient can also create friction in real-world systems. Review collected by and hosted on G2.com.

Automating event based small task, Lambda is the way to go. Used it in multiple project totally reliable and helps in saving cost. Review collected by and hosted on G2.com.

There's a time and storage limit on processing, which sometimes act as blocksr Review collected by and hosted on G2.com.

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.