AWS Lambda Reviews & Product Details

It’s serverless, so we don’t have to worry about managing servers—AWS handles that for us. We use AWS Lamda for running our performance tests, we don't have to keep server running, whenever we need we can spin up and run the tests for API's, good for short running tasks. Easy to maintain and integrate it from command line. Price wise also we don't spend much since it's costing us for what we run. Later to trouble shoot issues, we cna go to UI and check the aws cloudwatch logs, AI can help as well if we want are trougble shooting something specific, and onboarding same process for other env is easy. Review collected by and hosted on G2.com.

I wish it could support more than 15 minutes; if they could extend it to 30 minutes, that would be great. Also, it takes a while to bootstrap and start running. 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.

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.

From my experience, what I like most about AWS Lambda is that it removes the need to manage infrastructure while automatically scaling with demand, integrates seamlessly with other AWS services, and provides a cost-efficient way to build and run event-driven workloads. Review collected by and hosted on G2.com.

The limits:

- The size limit of 250 MB.

- The concurrency limit issue.

- The limited supported programming languages Review collected by and hosted on G2.com.

It’s truly a zero-administration, serverless model, so there’s no need to manage hardware or worry about patching the operating system. It allows me and my team to focus 100% on writing code instead of spending time on server maintenance and ongoing upkeep. Review collected by and hosted on G2.com.

Debugging and observability: When you’re debugging but don’t have access to the underlying server, you can’t SSH in to see what’s wrong, which makes troubleshooting much harder. Review collected by and hosted on G2.com.

The best part of AWS Lambda is that there’s essentially zero server management. Not having to patch OS versions or manage clusters lets our engineering team focus fully on writing and improving code instead of dealing with infrastructure overhead. The event-driven model also feels seamless—triggering functions from S3 uploads, DynamoDB changes, or API Gateway requests simply works as expected. On top of that, the scaling is impressive: whether we see 10 requests or 10,000, Lambda handles the concurrency without us needing to tweak a single scaling policy. Review collected by and hosted on G2.com.

The “Cold Start” issue is still a factor, particularly for functions written in Java or .NET, and it can add slight latency when requests are infrequent. In addition, the 15-minute execution limit means it isn’t a great fit for long-running or heavy data-processing tasks. With these constraints in mind, you really have to be intentional about how you design and architect your workflows so everything stays within the guardrails. Review collected by and hosted on G2.com.

AWS Lambda makes it easy to run code without managing servers. I like how it automatically scales based on demand and only charges for actual execution time, which helps reduce infrastructure cost. It integrates very well with other AWS services like API Gateway, S3, SQS, and DynamoDB, making it simple to build event-driven architectures. Deployment is fast, and for microservices or background jobs it saves a lot of operational overhead compared to managing EC2 instances. Review collected by and hosted on G2.com.

Cold starts can sometimes impact performance, especially for VPC-based or larger functions. Review collected by and hosted on G2.com.

AWS Lambda's serverless scaling handled our 10k req/sec spikes perfectly, cutting costs 60% vs. EC2. Quick Python setup, seamless DynamoDB integration. Cold starts fixed with concurrency; minor timeout limits.​

Pros: Auto-scale, pay-per-use.

Cons: VPC latency.

Highly recommend! Review collected by and hosted on G2.com.

AWS Lambda has notable limitations like cold starts that delay initial function invocations. The 15-minute execution timeout restricts longer-running tasks.

Main Drawbacks

Monitoring can feel fragmented without third-party tools, complicating debugging in complex apps. VPC integration adds latency and setup overhead.

Vendor Lock-in

Heavy reliance on AWS services reduces portability to other clouds. Deployment package size limits (250 MB unzipped) hinder large dependencies. Review collected by and hosted on G2.com.

I like most about the AWS lambda is .

1. It'server less execution means no need to provision or manage server .

2.This functions run only on when triggered(s3upload,API gateway request) .

3. cost effective , we need to pay only for the compute time. Review collected by and hosted on G2.com.

Dislike about AWS Lambda are

1. Slow start, functions are takes extra time during initialization .

2.Long time execution limits .

3.Complex in debugging the functions . Review collected by and hosted on G2.com.