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’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.

AWS Lambda is easy to use and simple to implement, especially for event-driven workflows. It integrates seamlessly with other AWS services, which makes building automation and serverless APIs very smooth. We use it frequently for scheduled jobs and lightweight backend tasks. The feature set is strong, with support for layers, versioning, and multiple runtime options. Customer support is decent, backed by solid documentation, although response times can vary. Overall, Lambda is a reliable and efficient serverless compute option. Review collected by and hosted on G2.com.

Cold starts can be frustrating at times, and debugging or monitoring distributed serverless functions is harder compared to traditional applications. Review collected by and hosted on G2.com.

AWS handles all the operational heavy lifting, including provisioning, patching, OS maintenance, and capacity management.You are only charged for the actual time your code executes, billed in 100-millisecond increments.Lambda functions are easily triggered by a wide variety of events from over 200 other AWS services.Lambda runs your code on a highly available compute infrastructure and manages fault tolerance across multiple Availability Zones, ensuring high resilience without extra effort.This allows developers to focus entirely on writing application logic. Review collected by and hosted on G2.com.

Functions have a maximum execution time of 15 minutes, limiting their use for heavy, long-running batch jobs.Because code runs in a managed, ephemeral environment, attaching debuggers is impossible. Local testing is difficult to mirror properly.Leveraging framework tools (e.g., SAM, Serverless Framework) helps manage configuration and deployment, though it doesn't solve the core debugging issues.Unlike a persistent server, Lambda creates a new environment for concurrent requests. Review collected by and hosted on G2.com.

I love that AWS Lambda lets us run our code without managing servers, making it an ideal choice for creating serverless services. Being a full-stack developer, it helps me build scalable backends and automate database queries efficiently. The ability to pay only for what I use is fantastic as it reduces costs and means I am only charged when my code is running. This 'pay as you use' model is preferred because it saves time on backend maintenance and lets us focus resources on more important tasks. The ease of integrating AWS Lambda with other services like S3 and API Gateway is a big plus for me. Additionally, setting it up was quite easy, thanks to the ample technical documents and videos available for learning. Review collected by and hosted on G2.com.

We can't use some other services alongside AWS Lambda like Azure or Google Cloud in a seamless way. The cold start takes a while to initialize. Review collected by and hosted on G2.com.

1. A serverless service, which can be used for automating the work. ex: volume backup, scheduling the stopping of unused servers

2. Implementation is easy; creating the function is very easy. and it lets u run code according to your coding language

3. As a user, we do not need to maintain; by default, AWS will manage.

4. Triggers can be added for the invocation of other services, such as s3, and event driven process

5. it reduces the human efforts for getting the reports from databases as well.

6. one function can be used for many types of work. Support for lambda is quick Review collected by and hosted on G2.com.

There are limitations that lambda can only execute for 15 min, if there is any function that needs to operate above 15 min then lambda is not suitable service. also the memory , disck space are limited only, thes which makes few operations tough Review collected by and hosted on G2.com.