No infrastructure management: You just deploy your function and AWS handles servers, scaling, and maintenance.

Automatic scaling: It scales instantly from zero to thousands of requests without configuration.

Cost efficiency: You only pay for execution time, not idle server time. Review collected by and hosted on G2.com.

Cold starts: Functions can have latency delays when they haven’t been used recently, which affects performance in time-sensitive apps.

Execution limits: There are strict timeouts (max runtime), memory constraints, and ephemeral storage limits, which make it unsuitable for long-running or heavy compute tasks. Review collected by and hosted on G2.com.

What I like most about AWS Lambda is that it allows you to execute business logic and automations without having to manage servers. It is very useful for building lightweight integrations, responding to events, and decoupling processes within an AWS architecture. I also appreciate that it integrates well with other services like S3, EventBridge, Step Functions, IAM, and CloudWatch, which greatly facilitates the construction of serverless workflows. For specific tasks, event processing, and auxiliary components of pipelines, it is very practical and scalable. Review collected by and hosted on G2.com.

What I like least is that debugging and troubleshooting can become more complex when the function depends on multiple services, permissions, or external configurations. There are also limitations that require careful design of certain use cases, such as maximum execution times, handling heavier packages, or specific dependencies. In some scenarios, monitoring errors or understanding integration failures takes longer than expected. Review collected by and hosted on G2.com.

You pay what you use, For projects with spiky traffic—like an app that only gets hits during business hours or special sale like Black Friday, this saves us a fortune. Review collected by and hosted on G2.com.

If you've ever tried to trace a single request across five different Lambda functions using CloudWatch's default UI, you know it's a nightmare. To get decent observability, you usually have to pay for a third-party tool like Datadog or New Relic, which adds another layer of cost.

Second, it should only cost for execution and not for cold start when code is actually waking up Review collected by and hosted on G2.com.

I use AWS Lambda to handle quick behind-the-scenes tasks like resizing uploaded profile pictures, sending automatic welcome emails, and processing credit card payments securely. What I really like is that you only pay when it's actively working, so if my app gets zero traffic, then my bill is zero. Lambda saves me from server issues and scales instantly during traffic spikes, which gives me zero stress after using it. I really like the pay-for-what-you-use model and how it scales automatically without my help. The ecosystem integration is another major thing that I like a lot about AWS Lambda. Automatic scaling keeps my application fast and responsive by handling sudden spikes in user traffic instantly without crashing. The pay-per-use model ensures I never waste money paying for idle servers when traffic drops. Together, they give me total peace of mind and keep my operation costs low. Setting up Lambda is incredibly easy; you just write your code, zip it up, and upload it directly to the AWS console. Review collected by and hosted on G2.com.

Yes there are somethings like which doesn't work as well for me like cold start cost money, no built in GPU painful debugging. AWS should stop charging for cold start setup time and offer built in low cost GPU support for AI task additionally they need to fix debugging by replacing messi hard to read tax log with the simple visual dashboard that instantly highlights exactly where and why my code correction. Review collected by and hosted on G2.com.

I like the simplicity and speed of development in AWS Lambda the most. I can quickly deploy a standalone function and immediately connect it to events without server setup. I also note the automatic scaling under load, the pay-per-execution model, and the tight integration with other AWS services. Review collected by and hosted on G2.com.

There are a couple of points: the time execution limitation by resources is not always convenient for heavier and longer tasks, debugging and tracing can be difficult to quickly understand problems without good CloudWatch configuration. Dependency on the AWS ecosystem - a strong link with other services sometimes complicates transferring them to other platforms. Initially, the setup was a bit more complicated than in GCP Cloud Run due to a larger number of low-level details. Deployment through CI/CD required more detailed configuration and proper setup of logging and monitoring through CloudWatch. Cold start, execution time limits, and more complex debugging in some scenarios. Review collected by and hosted on G2.com.

I like AWS Lambda because it's serverless and secure, especially since we can run it in a private subnet. It also provides a secure protocol URL for executing Lambda functions. It integrates very well with AWS services, making it efficient for our use. The initial setup is very easy, so even beginners can create serverless functions quickly. I also appreciate its impact on cost savings and incident resolution through automation. I think it's a 10 out of 10 service, especially for small teams or those relying on APIs, as it's secure and cost-effective. Review collected by and hosted on G2.com.

I think they need to improve at Security in public because if we put function in public then we don't have restriction like security group or this IPs can be call to Lambda. Right now we have to give our servers if we wanted security for Lambda but in Lambda itself we need a security group-like feature so we can restrict calling our Lambda by network or by IPs. Functions would be more secure if they are in a public subnet or directly connected with an internet gateway. Review collected by and hosted on G2.com.

I like AWS Lambda for its simplicity and scalability. It allows me to run code without managing servers and deploy very quickly, which is handy. I only pay for actual usage, which I find efficient. AWS Lambda is very useful for automation, API integrations, and handling workloads efficiently. It automatically handles changes in workloads, whether it's a few requests or a sudden spike in traffic, saving a lot of time and reducing operational effort. Also, the initial setup was fairly easy, especially for basic functions, thanks to AWS's straightforward console templates and good integrations with services like API Gateway and S3 buckets. Review collected by and hosted on G2.com.

I would say, one area that could be improved is cold start performance for some workloads. Especially when, functions are not evoked frequently. Because debugging across these multiple services can also take extra efforts in, like, complex architectures. And, better visibility and simple troubleshooting tools would make it even more efficient. Review collected by and hosted on G2.com.

it removes the need to manage servers and scales automatically with demand. The most helpful part is the pay-as-you-go model, where you’re only charged for the actual execution time, which makes it cost-efficient. Upsides include quick deployment, easy integration with other AWS services, and the ability to build event-driven applications without worrying about infrastructure. Review collected by and hosted on G2.com.

AWS Lambda is the cold start delay, which can impact performance for latency-sensitive applications. The least helpful part is the limited execution time and resource constraints, which make it harder to handle very heavy workloads. Downsides include vendor lock-in, debugging complexity, and the need to design carefully around its limits to avoid unexpected issues. Review collected by and hosted on G2.com.

I like AWS Lambda because it’s event-driven, highly scalable, and can save a lot of money by charging only for actual execution time instead of keeping servers running continuously. I also like that it removes server management entirely and integrates easily with services like API Gateway, S3, and DynamoDB, which makes it efficient to build scalable, cost-effective applications. Review collected by and hosted on G2.com.

I don’t like that AWS Lambda cold-start latency, which hurts performance for infrequently used functions especially when an app is time-sensitive. Review collected by and hosted on G2.com.

I really appreciate the ability to quickly build scalable event-driven architectures without worrying about infrastructure provisioning or scaling. The serverless execution with automatic scaling is fantastic, and I find AWS Lambda very efficient for event-driven workloads. It handles scaling without the need for server management, which is a huge plus for me. Review collected by and hosted on G2.com.

It has a hard limitation on the timing and the speed on the storage. Cold start latency can affect performance for some workloads. Debugging distributed serverless systems can become challenging. Managing permissions, deployment, and packaging is a little complicated and tricky. Complex event chains also require experience. Review collected by and hosted on G2.com.