# AWS Lambda Reviews
**Vendor:** Amazon Web Services (AWS)  
**Category:** [Cloud Platform as a Service (PaaS) Software](https://www.g2.com/categories/cloud-platform-as-a-service-paas)  
**Average Rating:** 4.6/5.0  
**Total Reviews:** 1,038
## About AWS Lambda
AWS Lambda lets you run code without provisioning or managing servers. You pay only for the compute time you consume - there is no charge when your code is not running. With Lambda, you can run code for virtually any type of application or backend service - all with zero administration. Just upload your code and Lambda takes care of everything required to run and scale your code with high availability. You can set up your code to automatically trigger from other AWS services or call it directly from any web or mobile app.



## AWS Lambda Pros & Cons
**What users like:**

- Users find AWS Lambda to be **easy to use** , allowing quick implementation with serverless architecture and minimal maintenance. (47 reviews)
- Users value the **automatic scaling** of AWS Lambda, enabling efficient handling of unpredictable workloads with minimal management. (35 reviews)
- Users value the **cost-effective pricing** of AWS Lambda, appreciating its efficiency for handling varying workloads without extra charges. (27 reviews)
- Users appreciate the **flexibility and scalability** of AWS Lambda, simplifying code execution without server management. (23 reviews)
- Users appreciate the **seamless integrations** of AWS Lambda with other AWS services, enhancing development speed and efficiency. (22 reviews)
- Easy Setup (19 reviews)
- Automation (13 reviews)
- Deployment Ease (10 reviews)
- Reliability (10 reviews)
- Implementation Ease (9 reviews)

**What users dislike:**

- Users find the **resource limitations** of AWS Lambda restrict its use for larger datasets and heavy workloads. (36 reviews)
- Users find **difficult debugging** in AWS Lambda challenging due to its abstracted environment and reliance on logs for issue tracing. (17 reviews)
- Users are frustrated by the **slow performance** due to cold starts, impacting the responsiveness of their applications. (13 reviews)
- Users experience **lagging performance** due to slow initialization and execution time limits, impacting efficiency and usability. (10 reviews)
- Users find AWS Lambda to be **expensive** due to high costs compared to competitors and potential for unexpected charges. (9 reviews)
- Limitations (7 reviews)
- Users note that **complexity in configuration and dependency on external services** can hinder effective use of AWS Lambda. (5 reviews)
- Missing Features (3 reviews)
- Scaling Issues (3 reviews)
- Cost Transparency (2 reviews)

## AWS Lambda Reviews
  ### 1. Serverless Simplicity: Easy Scaling and Pay-Per-Use with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** Jeyaganapathy N. | CloudOps Engineer - Associate , Small-Business (50 or fewer emp.)

**Reviewed Date:** June 08, 2026

**What do you like best about AWS Lambda?**

The best part about AWS Lambda is that it allows you to run code without the need for managing servers. It automatically handles the scaling and execution which makes it very easy for event driven workloads.
Additionally, the pricing model is very low as we need to pay only for the compute time your code actually runs.

**What do you dislike about AWS Lambda?**

One thing that i disliked about AWS Lambda is the execution limit, which makes it less suitable for running long process. Debugging can also be slighty difficult compared to the tradition server rest all if fine

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda helps me reducing the cost required for compute task instead or running the server we can use lambda to run only when the trigger gets hit which allow you to pay only the execution of the code it is code based helps us to automate serveral task like starting or stop a server at particular time daily or delete some things over the shedule period. do particular action based on the triggered actions all type of automation is possible due to lambda

  ### 2. AWS Lambda Transformed Our Event-Driven Automation

**Rating:** 4.5/5.0 stars

**Reviewed by:** Bibhishan D. | QA Lead, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** June 02, 2026

**What do you like best about AWS Lambda?**

As a DevOps/SRE engineer, AWS Lambda has completely transformed how we handle event-driven automation.
The ability to trigger functions in response to AWS events — whether it's an S3 upload, an SNS notification, a CloudWatch alarm, or a DynamoDB stream — without provisioning or managing any servers is incredibly powerful.
The pay-per-invocation pricing model means we're not paying for idle compute, which has noticeably reduced our cloud costs.

**What do you dislike about AWS Lambda?**

The cold start latency can be a challenge, especially for latency-sensitive automation tasks that aren't invoked frequently.
While Provisioned Concurrency helps, it adds cost. Also, the 15-minute execution limit means Lambda isn't suitable for long-running jobs — for those, we still rely on ECS or Step Functions.
Debugging complex multi-function workflows can also get tricky without proper distributed tracing set up via X-Ray.

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda has allowed our team to build scalable, event-driven automation pipelines without the overhead of managing dedicated infrastructure.
It has freed up our SRE team to focus on higher-value reliability work rather than babysitting servers. Overall, it's become a core part of our automation toolkit on AWS.

  ### 3. Serverless, Cost-Effective Performance Testing with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** Chetan M. | Software Engineer, Enterprise (> 1000 emp.)

**Reviewed Date:** April 02, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

We use AWS Lambda to run our performance tests, which is very important because our app has been live for 5 years and customers use it every day. Every quarter, we run performance tests to make sure our APIs meet our SLA metrics. AWS Lambda is very helpful for getting these stats and covering this scenario for us.

  ### 4. Simple and Efficient Serverless Computing

**Rating:** 4.5/5.0 stars

**Reviewed by:** Navin N. | Devops engineer, Computer Software, Mid-Market (51-1000 emp.)

**Reviewed Date:** June 09, 2026

**What do you like best about AWS Lambda?**

What I like most about AWS Lambda is how easy it makes running applications without worrying about servers. It automatically scales based on demand, saves time on infrastructure management, and helps reduce costs because you only pay when your code runs. It integrates smoothly with other AWS services, making development much faster and simpler.

**What do you dislike about AWS Lambda?**

One thing I dislike about AWS Lambda is that debugging and troubleshooting can sometimes be challenging, especially for complex applications. Cold starts may also cause slight delays for infrequently used functions, and managing execution time limits can be restrictive for long-running workloads. However, for most use cases, the benefits outweigh these limitations.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves the problem of managing and maintaining servers for running applications and backend processes. Instead of spending time on infrastructure, I can focus on writing code and delivering features. It automatically scales based on demand and follows a pay-per-use model, which helps reduce operational effort and costs. This allows me to develop and deploy applications faster while improving overall efficiency.

  ### 5. AWS Lambda: Seamless Event-Driven Automation with S3, CloudWatch, and API Gateway

**Rating:** 5.0/5.0 stars

**Reviewed by:** mani s. | data engineer, Enterprise (> 1000 emp.)

**Reviewed Date:** May 26, 2026

**What do you like best about AWS Lambda?**

I frequently use AWS Lambda in our project. We mainly use it for event-driven automation in our workflow. The best part is that once files arrive in S3, we’ve set it up to trigger automatically. This then automates the validation process, which I like the most. On top of that, its integration with other AWS tools is fast.

**What do you dislike about AWS Lambda?**

I don’t have any major dislikes about AWS Lambda. Overall, it’s a good product and has worked well for me.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda helps solve problems like automating recovery and monitoring when workflow failures happen. For example, if some files don’t arrive at the expected time, AWS Lambda can trigger notifications and send alert messages so I can respond quickly.

  ### 6. Easy to Configure, Powerful Fan-Out Scaling, and Seamless AWS Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Dhaval C. | Senior Technical Architect, Small-Business (50 or fewer emp.)

**Reviewed Date:** May 06, 2026

**What do you like best about AWS Lambda?**

It is easy to configure. It has lots of user controls like run time, timeout, source event, layers, and it is pay-as-you-go. It gives immense power for fan-out scaling. Also, it is compatible with lots of AWS native services and integrates well with them, like API Gateway, S3, SNS, SQS, CloudWatch, and many more

**What do you dislike about AWS Lambda?**

Lambda has an upper limit on runtime, so you will have to design your system accordingly. Also, debugging becomes quite messy because there will be many invocations happening simultaneously.

**What problems is AWS Lambda solving and how is that benefiting you?**

For us, separation of concern in case of event, Event-driven architecture,
we don't have to worry about infra, as it is already taken care of by AWS. It supports all major runtimes and is well-documented, so getting community or dedicated support is easy.

  ### 7. Well-Supported, Well-Documented Tool for Running Background Jobs on AWS

**Rating:** 5.0/5.0 stars

**Reviewed by:** Adam E. | Solutions Integration Engineer, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** May 20, 2026

**What do you like best about AWS Lambda?**

It is a very well supported tool that provides great infrastructure for running background jobs and tasks periodically. It has great support with other AWS services and is easy to run with a lot of great documentation.

**What do you dislike about AWS Lambda?**

I don’t like that the maximum function time is limited to 15 minutes. I really hope this can be increased, because it doesn’t always accommodate bigger jobs.

**What problems is AWS Lambda solving and how is that benefiting you?**

It is allowing us to deploy integrations and jobs that run periodically in an easy and lightweight manner. It provides a great way to set up these background functions without needing to delve into the setup or server configuration and is easy to troubleshoot and connect to other services such as S3 and Cloudwatch.

  ### 8. Native AWS Event Integrations That Make Shipping Microservices Fast

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** May 31, 2026

**What do you like best about AWS Lambda?**

The native, abstract integration with the AWS event ecosystem.
Lambda feels like the ultimate connective tissue. Rather than writing boilerplate polling logic or managing persistent connections, you get clean, out-of-the-box event mappings for S3 hooks, DynamoDB Streams, SQS queues, and Kinesis. Being able to write a tightly focused handler function and then let the platform handle upstream ingestion, batch sizing, and retry behavior out of the box completely changes how quickly you can ship decoupled microservices.

**What do you dislike about AWS Lambda?**

The most frustrating part of working with AWS Lambda, for me, is dealing with its architectural guardrails—especially cold starts and the strict 15-minute execution limit. For synchronous, user-facing APIs, a cold start can cause a noticeable latency spike, and it’s even worse when the function runs inside a VPC. That reality forces careful mitigation (like Provisioned Concurrency), but doing so undercuts the “scale-to-zero” cost benefit.

On top of that, the hard timeout means Lambda simply isn’t a fit for long-running batch jobs or continuous processing. You end up having to split work into more complex, decoupled Step Functions workflows or offload it to ECS/Fargate, which adds architectural complexity that feels unnecessary.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda removes a lot of the headache of undifferentiated heavy lifting by abstracting away server management, capacity planning, and the complexity of event-polling infrastructure. Rather than spending time provisioning VMs, tuning auto-scaling policies, or writing boilerplate code just to consume queues, Lambda serves as native, event-driven glue that automatically scales from zero to thousands of concurrent requests as traffic comes in. For developers, this means you can focus squarely on core business logic, ship changes faster, and optimize infrastructure spend with a true pay-per-use, millisecond-precision billing model—so you’re not paying for idle compute.

  ### 9. Effortless Scalability for Modern Backend Workloads

**Rating:** 4.0/5.0 stars

**Reviewed by:** Andrés M. | Front-End Development Analyst I, Small-Business (50 or fewer emp.)

**Reviewed Date:** April 30, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

olves the problem of having to manage, scale, and maintain servers for backend workloads. Traditionally, teams needed to provision infrastructure, handle scaling, apply updates, and keep servers running—even when idle. Lambda removes that entire operational layer by running code only when it’s needed.

  ### 10. AWS Lambda simplifies automation and the execution of serverless logic

**Rating:** 4.5/5.0 stars

**Reviewed by:** Caleb F. | Data &amp; IA Specialist, Small-Business (50 or fewer emp.)

**Reviewed Date:** March 10, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda helps address the need to run processes on demand or event-based without provisioning or maintaining infrastructure. In my case, it is useful for automations, middleware logic between services, and auxiliary tasks within data flows and operational processes in AWS. The main benefit is that it reduces operational load, accelerates the development of integrations, and allows for building scalable components in a simpler and more flexible way.

  ### 11. Efficient Scaling with Cost-Effective Pricing

**Rating:** 4.5/5.0 stars

**Reviewed by:** Rittik G. | Programmer Analyst Trainee, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 16, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

I use AWS Lambda to handle tasks like resizing images, sending emails, and processing payments. It saves me from server issues, scales during traffic spikes, and charges only for active use, keeping my costs low.

  ### 12. Simplicity and integration with AWS, but there are limitations

**Rating:** 4.0/5.0 stars

**Reviewed by:** Vitalii B. | Python Developer, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 13, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda removes the tasks of server and infrastructure management, allowing you to focus on code. It simplifies scalability and the building of event-driven architecture, reduces costs by charging only for actual execution, and speeds up the development and deployment of independent functions.

  ### 13. Cost-Effective Serverless Solution with Room for Security Enhancements

**Rating:** 5.0/5.0 stars

**Reviewed by:** Het T. | Employer, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 07, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda automates our infrastructure for cost savings and efficiently handling incidents with custom logic. It helps with cost optimization and automation, solving these problems effectively.

  ### 14. Effortlessly Scalable and Efficient Serverless Computing

**Rating:** 4.5/5.0 stars

**Reviewed by:** Avni G. | Cloud Engineer 3, Enterprise (> 1000 emp.)

**Reviewed Date:** April 28, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

I use AWS Lambda for serverless automation tasks, API integrations, and event-driven processing, which saves time, reduces infrastructure overhead, and handles traffic spikes without managing servers. It scales automatically, making deployment faster and more efficient.

  ### 15. AWS Lambda be Severless

**Rating:** 4.0/5.0 stars

**Reviewed by:** Pushpraj k. | Devops Engineer, Computer Software, Small-Business (50 or fewer emp.)

**Reviewed Date:** September 19, 2025

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

solves the problem of managing servers and infrastructure for small services or event-driven tasks. It lets me focus on writing code while automatically handling scaling, availability, and execution in response to events. This benefits me by reducing operational overhead, lowering costs, and speeding up development, since I can quickly build and deploy functions without worrying about servers.

  ### 16. Scalable, Cost-Effective Serverless Apps with AWS Lambda

**Rating:** 4.5/5.0 stars

**Reviewed by:** Anup k. | Associate Cloud Engineer, Small-Business (50 or fewer emp.)

**Reviewed Date:** April 28, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

I don’t like that AWS Lambda cold-start latency, which hurts performance for infrequently used functions especially when an app is time-sensitive.

**What problems is AWS Lambda solving and how is that benefiting you?**

I only pay when my code runs. I like that this saves a lot of money, especially for workloads that don’t run constantly, and I don’t have to worry about over-provisioning resources.

  ### 17. Pay-as-You-Go Savings That Shine for Spiky Traffic

**Rating:** 4.5/5.0 stars

**Reviewed by:** Prince S. | Senior Consultant, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 11, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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

**What problems is AWS Lambda solving and how is that benefiting you?**

NO estimation of number of servers , no management for servers, If we get 1 hit or 10,000 hits at the same moment, Lambda just handles the provisioning. It has essentially removed server downtime due to traffic from my list of things to worry about.

  ### 18. Streamlined, Cost-Effective Event-Driven Processing

**Rating:** 4.5/5.0 stars

**Reviewed by:** Atharva P. | Cloud BI Engineer, Enterprise (> 1000 emp.)

**Reviewed Date:** May 08, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda helps us avoid the need for other tools for event-driven processing, eliminates server management overhead, and enables scalable execution for microservices. It saves costs with hardware-less execution and automatic scaling, making it efficient for event-driven workloads.

  ### 19. Effortless Scaling and Cost-Efficient Event-Driven Workloads with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** Nidal S. | Senior DevOps Engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 28, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

The limits:

- The size limit of 250 MB.

- The concurrency limit issue.

- The limited supported programming languages

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves the need to provision and manage servers for event-driven workloads, allowing me to focus on building logic instead of infrastructure, which speeds up development, reduces operational overhead, and keeps costs low by only paying for actual execution time.

  ### 20. Simple, Flexible, and Cost-Effective Serverless Scaling with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** Sayed  M. | Consultant, Mid-Market (51-1000 emp.)

**Reviewed Date:** May 23, 2026

**What do you like best about AWS Lambda?**

I like its simplicity and flexibility for running applications without having to manage servers. It scales automatically based on traffic, which makes deployments faster and more efficient. The pay-as-you-use pricing model also feels cost-effective, since you only pay for the actual execution time. Another big advantage is how smoothly it integrates with other AWS services, making it easier to build event-driven, highly automated workflows while keeping infrastructure management to a minimum.

**What do you dislike about AWS Lambda?**

At the moment, I don’t have any major concerns with AWS Lambda.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda removes the need for server maintenance, which makes deployment simpler and faster.

It also scales automatically with changing workload demands, helping maintain reliable performance.

With its pay-per-use pricing model, I can avoid paying for unnecessary infrastructure and keep costs under control.

  ### 21. Serverless Efficiency with Seamless AWS Integration

**Rating:** 4.0/5.0 stars

**Reviewed by:** Vikas N. | System Engineer, Enterprise (> 1000 emp.)

**Reviewed Date:** May 26, 2026

**What do you like best about AWS Lambda?**

I like AWS Lambda's serverless architecture and automatic scaling. It's great how it seamlessly integrates with AWS services, which significantly reduces infrastructure overhead. This really speeds up the backend development and deployment. AWS Lambda is effective because it eliminates the need to manage and maintain servers for backend applications. I appreciate how it automatically handles scaling, infrastructure management, and the execution of code based on events, reducing operational effort and infrastructure costs. It also enables fast deployment and development.

**What do you dislike about AWS Lambda?**

One of the limitations I've faced is the cold start latency for some workloads, and the complexity that can arise when debugging serverless applications.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda eliminates infrastructure management, enables fast deployment, and handles automatic scaling for event-driven applications, lowering costs and speeding backend development.

  ### 22. True Zero-Administration Serverless Model That Lets Us Focus on Coding

**Rating:** 4.0/5.0 stars

**Reviewed by:** Muhammad Awais  A. | Sr ICT Engineer, Information Technology and Services, Small-Business (50 or fewer emp.)

**Reviewed Date:** January 24, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

Traditionally, a small script to monitor a network or check a license required a dedicated server or VM, which then needed OS patching, security hardening, and ongoing monitoring. With Lambda, I can deploy code to handle a specific task without managing the underlying infrastructure. This removes the overhead of maintaining utility servers, and lets me run automation scripts for infrastructure without the burden of patching and maintaining a Linux box just to host a single Python script.

  ### 23. Zero Server Management and Seamless Auto-Scaling with AWS Lambda

**Rating:** 4.5/5.0 stars

**Reviewed by:** Chandan D. | Staff Software Development Engineer Test, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** January 14, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda has helped us solve our infrastructure cost problem. Before, we were paying for EC2 instances that sat idle for about 60% of the day. After moving to a pay-as-you-go model, we now pay only for the exact milliseconds our code is running, which has reduced our compute costs by nearly 40%. It has also improved our “Time to Market,” since we can deploy microservices in minutes without having to coordinate with an Ops team.

  ### 24. AWS Lambda: Effortless Serverless Scaling and Seamless AWS Integrations

**Rating:** 5.0/5.0 stars

**Reviewed by:** Shahzaib R. | Associate DevOps Engineer, Small-Business (50 or fewer emp.)

**Reviewed Date:** February 02, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

Cold starts can sometimes impact performance, especially for VPC-based or larger functions.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda removes the need to provision, manage, and scale servers for running application logic. Instead of maintaining EC2 instances, patching OS, and handling auto-scaling, Lambda lets us focus only on writing code. It’s especially useful for handling event-driven workloads like API backends, file processing from S3, background jobs, and integrations between services.

  ### 25. Cost-Effective with Event-Based Scaling

**Rating:** 5.0/5.0 stars

**Reviewed by:** Keyur T. | Mobile app developer, Information Technology and Services, Small-Business (50 or fewer emp.)

**Reviewed Date:** April 29, 2026

**What do you like best about AWS Lambda?**

I like using AWS Lambda because it's cost-effective with event-based triggers and offers fast servers. It's great that I don't need to panic about load since it automatically handles our cloud infrastructure's auto-scaling based on the traffic. The billing based on usage, especially for our website with time-based traffic, helps manage costs efficiently. Also, the initial setup was very easy, which was a plus.

**What do you dislike about AWS Lambda?**

They don't have a cPanel, we need to do all using SSH and command line. I think they need to build a cPanel.

**What problems is AWS Lambda solving and how is that benefiting you?**

I use AWS Lambda for hosting and managing cloud infrastructure with auto-scaling and event-based triggers, like CI/CD. It's cost-effective, handles high traffic effortlessly, and charges based on usage, freeing me from worrying about load.

  ### 26. Effortless Scaling and Cost Savings with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** Gagan G. | Application Developer, Mid-Market (51-1000 emp.)

**Reviewed Date:** December 15, 2025

**What do you like best about AWS Lambda?**

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!

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves serverless compute challenges by eliminating server provisioning, management, and scaling needs.​

Core Problems Addressed
It handles infrastructure overhead, allowing focus on code for faster development cycles. Automatic scaling manages traffic spikes without manual intervention.​

Key Benefits
Pay-per-use pricing cuts costs for idle time, while built-in high availability boosts reliability. This accelerates innovation and reduces operational burden.​

  ### 27. Cost-Effective Serverless Execution with AWS Lambda

**Rating:** 4.5/5.0 stars

**Reviewed by:** Subrajit B. | Deputy Manager, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** February 11, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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 .

**What problems is AWS Lambda solving and how is that benefiting you?**

Main problems it solves .
1.Server management overhead : no patching ,provisioning, scaling tension because of lambda function .
2.It resolves the scalability challenges on more load it scale sit self .
3.Cost efficiency - we need to pay only for it's computation .

  ### 28. Effortless Serverless Computing with Seamless AWS Integration

**Rating:** 5.0/5.0 stars

**Reviewed by:** Manil G. | Software engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** December 02, 2025

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

Cold starts can be frustrating at times, and debugging or monitoring distributed serverless functions is harder compared to traditional applications.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda helps us eliminate server management for small services and automation tasks. It solves the problem of scaling and infrastructure overhead by automatically handling load, letting us focus only on the code. It’s especially useful for scheduled jobs, event-driven workflows, and API backends, which has reduced our operational effort and overall costs.

  ### 29. Seamless AWS Bedrock & Salesforce Integration with Smooth Deployments and Logging

**Rating:** 4.0/5.0 stars

**Reviewed by:** Parth P. | Developer, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 16, 2026

**What do you like best about AWS Lambda?**

The connectivity with aws bedrock and also the interation with the other resource and also the lex connectivity with the salesforce and the code deployment and logs

**What do you dislike about AWS Lambda?**

The logs which we get is often takes time somtimes to update and also the code testing in the enviroment is taking time to debug and give the output.

**What problems is AWS Lambda solving and how is that benefiting you?**

The integration and the connectivity with the lex bot and also the bedrock prompt including the connectivity with other system like salesforce.

  ### 30. AWS Lambda Takes the Operational Heavy Lifting Off Your Plate

**Rating:** 5.0/5.0 stars

**Reviewed by:** Himanshi M. | Team lead software engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** February 02, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda scales horizontally in response to incoming events. Whether you have one request or thousands per second, the service creates new execution environments to handle the load instantly without manual configuration.Unlike traditional servers (EC2) where you pay for uptime regardless of usage, Lambda bills only for actual execution time rounded to the nearest millisecond.Triggering a welcome email whenever a new user is added to a database.Replacing traditional cron jobs with scheduled serverless functions for automated backups or reports.

  ### 31. Effortless Serverless Computing with AWS Lambda

**Rating:** 4.5/5.0 stars

**Reviewed by:** PRANSHU R. | Associate Software Developer, Mid-Market (51-1000 emp.)

**Reviewed Date:** January 29, 2026

**What do you like best about AWS Lambda?**

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.

**What do you dislike about AWS Lambda?**

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.

**What problems is AWS Lambda solving and how is that benefiting you?**

I use AWS Lambda to create a serverless service, running code without server management. It helps build scalable backends, automates database queries, and processes data. Its pay-as-you-use model cuts costs, and fast deployment saves time, allowing integration with services like S3 or API Gateway.

  ### 32. Effortless Serverless Deployments with AWS Lambda

**Rating:** 4.5/5.0 stars

**Reviewed by:** Amit G. | Graduate Research And Teaching Assistant, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 29, 2026

**What do you like best about AWS Lambda?**

I like that AWS Lambda is serverless, which makes for quick and easy deployment of services in the cloud. It integrates with a lot of other tools, which is really handy. I also appreciate the many features it offers for deploying code, like versioning, a built-in IDE, APIs, and AWS command access. Setting it up was pretty easy too.

**What do you dislike about AWS Lambda?**

Sometimes the boot-up time is slow. Also, maybe provide a free tier package, for deploying small functions with low traffic.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda makes cloud service deployment quick and easy. It's serverless, integrates with many tools, and offers features like versioning and a built-in IDE.

  ### 33. User-Friendly, Cost-Efficient Serverless Architecture with Easy Language Integrations

**Rating:** 3.5/5.0 stars

**Reviewed by:** GOURAV R. | Senior Associate-DevOps, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 22, 2026

**What do you like best about AWS Lambda?**

It integrates by default with other languages like Python, Node, etc. It offers a complete serverless architecture, which makes it user-friendly. We don’t need to worry about CPU, RAM, or storage issues, and it’s also cost-efficient.

**What do you dislike about AWS Lambda?**

As of nothing to dislike everything is in the right path

**What problems is AWS Lambda solving and how is that benefiting you?**

Their serverless design is cost-effective, since they charge only based on the number of requests. Also it comes with AWS quick support

  ### 34. Effortless Automation and Easy Integration with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** Pavan kumar S. | Cloud Engineer, Small-Business (50 or fewer emp.)

**Reviewed Date:** November 06, 2025

**What do you like best about AWS Lambda?**

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

**What do you dislike about AWS Lambda?**

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

**What problems is AWS Lambda solving and how is that benefiting you?**

volume back up, volume deletion which are more than 90days, and we can stop/terminate the un used servers, notification purpose
fualt tollerance, alerting the consultunts on production issues. Theese benifty me in day to day life and reduce human effort to check each and every minute.

  ### 35. Simplified Serverless Computing with Minor Delay Challenges

**Rating:** 3.5/5.0 stars

**Reviewed by:** Nityanand  C. | AWS Cloud Engineer , Mid-Market (51-1000 emp.)

**Reviewed Date:** April 29, 2026

**What do you like best about AWS Lambda?**

I like AWS Lambda because it's simple and easy to run code without managing the server. It's scalable and cost-effective. I also like how easily AWS Lambda integrates with other AWS services, including S3, API Gateway, and DynamoDB. The initial setup was fairly straightforward for our team.

**What do you dislike about AWS Lambda?**

Cold start delay doesn't always work well, which can slow things down a bit, especially for the function that aren't invoked often.

**What problems is AWS Lambda solving and how is that benefiting you?**

I use AWS Lambda to run backend code, automate tasks, and handle traffic spikes without managing servers. It's scalable, cost-effective, and integrates smoothly with services like S3, API Gateway, and DynamoDB.

  ### 36. Efficient serverless compute with seamless AWS integration

**Rating:** 5.0/5.0 stars

**Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.)

**Reviewed Date:** January 16, 2026

**What do you like best about AWS Lambda?**

AWS Lambda makes it easy to run code without managing servers, which significantly reduces operational overhead. Implementation is fast, especially when integrated with other AWS services like API Gateway, S3, and DynamoDB. It scales automatically, supports frequent use for event-driven workloads, and offers a strong set of features for building modern, serverless applications. The pay-per-use pricing model is efficient, and AWS documentation and support are reliable.

**What do you dislike about AWS Lambda?**

Debugging and monitoring can be challenging compared to traditional server-based applications, especially for complex workflows. Cold start latency can impact performance for certain use cases, and local development and testing are not always straightforward. While integration within AWS is excellent, portability outside the AWS ecosystem is limited.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves the problem of managing and scaling infrastructure for lightweight and event-driven workloads. It enables faster development cycles, reduces infrastructure costs, and allows teams to focus on business logic instead of server management. This results in quicker deployments, improved scalability, and better resource efficiency.

  ### 37. AWS Lambda: Easy to Use, Feature-Rich, and Simple to Integrate

**Rating:** 5.0/5.0 stars

**Reviewed by:** Jonathan Miguel C. | Senior Software Developer, Logistics and Supply Chain, Mid-Market (51-1000 emp.)

**Reviewed Date:** February 20, 2026

**What do you like best about AWS Lambda?**

AWS Lambda is easy to use and straightforward to implement. It also offers a lot of features and is easy to integrate with other services.

**What do you dislike about AWS Lambda?**

Lambda functions are stateless by design, so they require external services for state management. Also, if a function hasn’t been used for a long time, it may experience a cold start.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves multiple problems around infrastructure management because AWS handles all the underlying infrastructure for you. It also helps with integrations by connecting natively with other AWS services, which makes it easier to build complex, event-driven architectures.

  ### 38. Serverless Simplicity with Seamless AWS Integrations

**Rating:** 4.5/5.0 stars

**Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.)

**Reviewed Date:** March 30, 2026

**What do you like best about AWS Lambda?**

What I like most about AWS Lambda is its serverless architecture, which removes the need to manage infrastructure. It lets me focus on writing and deploying code, without having to worry about provisioning, configuring, or maintaining servers.

Another big advantage is how smoothly it integrates with other AWS services such as S3, API Gateway, and CloudWatch. That integration makes it straightforward to build event-driven applications and automate workflows.

I also appreciate its scalability and cost efficiency. Lambda scales automatically based on demand and uses a pay-per-use model, so I’m only paying for the compute time I actually consume.

**What do you dislike about AWS Lambda?**

One of the biggest drawbacks of AWS Lambda is cold-start latency, especially for functions that aren’t invoked often. This can introduce small delays in response times, which may affect performance for real-time applications.

Another limitation is execution time and resource constraints. Lambda functions have a maximum runtime and restricted memory/CPU options, which can make them a poor fit for long-running tasks or resource-intensive workloads.

Debugging and monitoring can also be challenging. Although CloudWatch provides logs, tracing and troubleshooting issues across multiple Lambda functions and connected services can quickly become complicated, particularly in distributed architectures.

Finally, managing dependencies and deployment packages can be somewhat cumbersome, especially as applications grow larger.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves the problem of managing and scaling infrastructure for backend services. Traditionally, setting up servers, planning for scaling, and maintaining uptime takes significant effort and resources. Lambda reduces that overhead by letting my code run in a fully managed, serverless environment.

It also tackles the challenge of handling event-driven workloads efficiently. Rather than keeping services running continuously, functions are triggered only when needed (for example, on file uploads or API calls). This improves resource utilization and helps avoid unnecessary costs.

For me, this has led to faster development cycles and lower operational complexity. I can deploy small pieces of functionality quickly, automate workflows, and integrate services without worrying about infrastructure management. It also supports cost optimization because I only pay for actual execution time instead of paying for idle server capacity.

Overall, AWS Lambda lets me focus more on business logic and less on system maintenance, which improves both productivity and scalability.

  ### 39. AWS Lambda Makes Serverless Simple with Auto-Scaling and Pay-as-You-Go Efficiency

**Rating:** 4.5/5.0 stars

**Reviewed by:** Bishnu M. | Senior Project Manager, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** May 19, 2026

**What do you like best about AWS Lambda?**

I really like how AWS Lambda lets me run code without managing servers. The automatic scaling and pay‑as‑you‑go model make it simple and efficient to use.

**What do you dislike about AWS Lambda?**

The only small downside is that debugging can be a bit tricky at times, especially with cold starts. It’s not a major issue, but something to be aware of.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda helps us run code on demand without managing servers, which saves time and reduces overhead. It is especially useful for handling event driven tasks and scaling automatically when workloads spike.

  ### 40. Easy setup , support multiple platform and coding languages

**Rating:** 4.0/5.0 stars

**Reviewed by:** Malkinder S. | Staff engineer, CloudOps, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 28, 2026

**What do you like best about AWS Lambda?**

Lambda is serverless so there's no tension about compute and memory.
On demand pricing , means you pay as you go.
very minimal efforts to setup.
integration with python and other languages.

**What do you dislike about AWS Lambda?**

Timeout can be an issue sometime, not efficient for long running jobs.

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda is solving my day to day tasks which were used to be done manually.

  ### 41. Effortless ingestion of uncertain events and  autoscalling when required

**Rating:** 4.0/5.0 stars

**Reviewed by:** Verified User in Information Technology and Services | Mid-Market (51-1000 emp.)

**Reviewed Date:** April 30, 2026

**What do you like best about AWS Lambda?**

The most helpful thing about Lambda is its auto-scaling, since it can automatically scale up when there are more requests.

**What do you dislike about AWS Lambda?**

Sometimes there are batch jobs that run for more than 15 minutes, and Lambda has a 15-minute timeout. Because of that, Lambda becomes undesirable for heavy data processing.

**What problems is AWS Lambda solving and how is that benefiting you?**

We use AWS Lamda for ingesting file uploads to S3 buckets into our tables because we receive the file monthly, but we don’t know exactly when it will arrive. Lambda handles that uncertainty by triggering the job that ingests the file as soon as it comes in.

  ### 42. Effortless Scaling and Cost Savings with AWS Lambda

**Rating:** 5.0/5.0 stars

**Reviewed by:** anand p. | Sr. Engineering Manager, Information Technology and Services, Enterprise (> 1000 emp.)

**Reviewed Date:** January 06, 2026

**What do you like best about AWS Lambda?**

I love that I don’t have to worry about servers at all. I just write my code, upload it, and AWS runs it for me whenever it’s needed. It scales automatically if 1 person uses my app or 10,000 persons Lambda handles it without me doing anything extra. Plus, I only pay when the code actually runs, so it’s often cheaper than keeping a server running all the time.

**What do you dislike about AWS Lambda?**

Sometimes there is a small delay the first time a function runs, which can be an issue for real-time apps. Also, you can’t control the underlying server or install custom system-level software Lambda works best when your code fits neatly into its model.
And debugging or monitoring can be trickier than a regular server, though tools like CloudWatch help.

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda solves the problem of managing and scaling servers. Instead of spending time setting up, patching, or monitoring machines, I can focus on writing code that adds real value to the product. It’s great for tasks like processing files when they’re uploaded, handling web requests or running scheduled jobs.

  ### 43. Serverless + AWS: Smooth Triggers, Effortless Deployment, and Reliable Autopayments

**Rating:** 5.0/5.0 stars

**Reviewed by:** Javier C. | Full Stack developer, Education Management, Small-Business (50 or fewer emp.)

**Reviewed Date:** February 06, 2026

**What do you like best about AWS Lambda?**

The serverless works perfectly with AWS. I use a lot of triggers, and they work perfectly with my code. You can focus on code and deployment without worrying about handling the rest of the code. My experience with payment has been good, with the run code of autopayment.

**What do you dislike about AWS Lambda?**

When you use it a lot,it need time to start again and repsonse times also become slower

**What problems is AWS Lambda solving and how is that benefiting you?**

handling APIs easier and making Amazon S3 efficient to run the triggers and make the job schedules, building microservices, also is easier to use, highly perfomance on the cost and efficient

  ### 44. AWS Lambda removes the headache of managing servers.

**Rating:** 5.0/5.0 stars

**Reviewed by:** shanavaz a. | Cloud Engineer, Information Technology and Services, Mid-Market (51-1000 emp.)

**Reviewed Date:** January 22, 2026

**What do you like best about AWS Lambda?**

I like AWS Lambda because it runs code without managing servers scales automatically  and you only pay when it runs. It also works smoothly with others AWS services, making development faster and easier.implementation is easy.i have use lambda in my most of use case.

**What do you dislike about AWS Lambda?**

The debugging and monitoring can be harder compared to traditional servers and limited execution time.

**What problems is AWS Lambda solving and how is that benefiting you?**

I wanted to share some insights about AWS Lambda, as I believe it could significantly impact our development workflow. AWS Lambda removes the headache of managing servers and eliminates the worries associated with scaling. By utilizing it we could save time and reduce costs.

  ### 45. A Very Powerful Tool with Few Limitations

**Rating:** 4.5/5.0 stars

**Reviewed by:** Jason M. | Software Manager, Manufacturing, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 27, 2026

**What do you like best about AWS Lambda?**

Very powerful tool with not a lot of limitations

**What do you dislike about AWS Lambda?**

It's complexity to set up the first time.. a lot of documentation to filter/go through
Things change, so sometimes the documentation is dated

**What problems is AWS Lambda solving and how is that benefiting you?**

we use it to sync data between airtable and dynamoDB
we also use it to delete files based on dates and to resize images

  ### 46. AWS Lambda Fn helps in automation a lot. Easy to integrate with AI LLMs,  Best in cost as well

**Rating:** 5.0/5.0 stars

**Reviewed by:** Manish R. | IT Manager, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 29, 2026

**What do you like best about AWS Lambda?**

We can write any function in that and can integrate any where along with it's arn. Also can integrate with Open AI and Azure foundry.

**What do you dislike about AWS Lambda?**

Nothing, It's too easy to write also. I am using it from a long time

**What problems is AWS Lambda solving and how is that benefiting you?**

I am using it to Automate the IT security.
Using it for AI services.

  ### 47. Great Free Coding Tool with Easy Uploads, but need Paid if you want to upgrade your Project

**Rating:** 3.5/5.0 stars

**Reviewed by:** Tony P. | IT Specialist, Mid-Market (51-1000 emp.)

**Reviewed Date:** October 14, 2025

**What do you like best about AWS Lambda?**

Code is completely free and I have trial it with not require upgrade, it can be start, everytime, I can try to upload code with ZIP and image, it like AI and it will be complete code.
AWS Lambda shines with its ability to run code without provisioning or managing servers, making deployment incredibly fast and efficient. It automatically scales based on demand, so you only pay for what you use—down to the millisecond. Plus, its seamless integration with other AWS services like S3, DynamoDB, and API Gateway makes building complex applications surprisingly smooth.

**What do you dislike about AWS Lambda?**

AWS Lambda can become expensive at scale, especially when functions are invoked frequently or run for extended durations. The cost model—based on number of requests and execution time—can be hard to predict, making budgeting tricky for complex applications. Additionally, integrating Lambda with other AWS services may incur extra charges, increasing the overall product cost beyond just the function itself.

**What problems is AWS Lambda solving and how is that benefiting you?**

AWS Lambda solves the problem of server management by allowing developers to run code without provisioning or maintaining infrastructure. It eliminates the need to worry about scaling, as Lambda automatically adjusts to handle any number of requests. This serverless model reduces operational overhead and speeds up deployment, making development more agile. By charging only for actual compute time, it helps optimize costs, especially for applications with variable workloads. Overall, Lambda empowers developers to focus on writing code and building features rather than managing servers.

  ### 48. Cost-Effective and Scalable Solution for Asynchronous Tasks

**Rating:** 5.0/5.0 stars

**Reviewed by:** Ketmani P. | React Developer, Small-Business (50 or fewer emp.)

**Reviewed Date:** February 28, 2026

**What do you like best about AWS Lambda?**

I like using AWS Lambda for its cost-efficiency and ability to handle a big load, which saves money and improves performance when dealing with bulk, asynchronous tasks like image conversion. The pricing is great, and it offers a lot of servers, which is useful when running many tasks in parallel.

**What do you dislike about AWS Lambda?**

I don't really like their code editor and overall interface, it looks outdated. I use it mostly to quickly test changes without proper deploy, so it is not a big problem.

**What problems is AWS Lambda solving and how is that benefiting you?**

I use AWS Lambda for asynchronous jobs like image conversion. It saves money and improves performance by handling bulk tasks efficiently without maintaining idle servers. I appreciate its cost-effectiveness and ability to handle a lot of parallel tasks.

  ### 49. Fast, Cross-Platform Coding Language Support with Flexible Pay-as-You-Go Pricing

**Rating:** 4.5/5.0 stars

**Reviewed by:** Malkinder S. | Cloud Operations Engineer, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 28, 2026

**What do you like best about AWS Lambda?**

Coding language support,
cross platform support,
pay as you go pricing
fast performance with less compute power

**What do you dislike about AWS Lambda?**

Not suitable for long running jobs due to timeout issue.

**What problems is AWS Lambda solving and how is that benefiting you?**

Lambda is solving my repetitive tasks which i used to do manually with low efforts and without spending on EC2 compute price.

  ### 50. Developer-Friendly Micro-services Management

**Rating:** 4.5/5.0 stars

**Reviewed by:** Tom C. | Senior Fullstack Developer, Mid-Market (51-1000 emp.)

**Reviewed Date:** April 21, 2026

**What do you like best about AWS Lambda?**

It’s developer-friendly and makes microservices easy to manage, which helps keep things organized and straightforward.

**What do you dislike about AWS Lambda?**

Cold-start issues are often a painful thing to deal with and consider. Also for infrequent used lambda, it will become inactive, which is quite troublesome

**What problems is AWS Lambda solving and how is that benefiting you?**

It helps save costs and makes microservices easier to deploy, monitor, and manage.


## AWS Lambda Discussions
  - [What is the best way to test locally without additional frameworks like serverless, SAM or Chalice?](https://www.g2.com/discussions/what-is-the-best-way-to-test-locally-without-additional-frameworks-like-serverless-sam-or-chalice) - 1 comment, 1 upvote
  - [What is AWS Lambda used for?](https://www.g2.com/discussions/what-is-aws-lambda-used-for) - 3 comments
  - [Is AWS lambda a container?](https://www.g2.com/discussions/is-aws-lambda-a-container) - 3 comments
  - [What is AWS Lambda built on?](https://www.g2.com/discussions/what-is-aws-lambda-built-on) - 2 comments
  - [How does AWS Lambda work?](https://www.g2.com/discussions/how-does-aws-lambda-work) - 2 comments

- [View AWS Lambda pricing details and edition comparison](https://www.g2.com/products/aws-lambda/reviews?section=pricing&secure%5Bexpires_at%5D=2026-06-11+15%3A31%3A05+-0500&secure%5Bsession_id%5D=7e402149-9198-4a7e-ab0e-9ea908be3779&secure%5Btoken%5D=4337b4b90c723295f9a0bdf085ccecbf627473862884033b986dc5d106ab42ef&format=llm_user)
## AWS Lambda Integrations
  - [Airtable](https://www.g2.com/products/airtable/reviews)
  - [Amazon API Gateway](https://www.g2.com/products/amazon-api-gateway/reviews)
  - [Amazon Aurora](https://www.g2.com/products/amazon-aurora/reviews)
  - [Amazon CloudWatch](https://www.g2.com/products/amazon-cloudwatch/reviews)
  - [Amazon DynamoDB](https://www.g2.com/products/amazon-web-services-aws-amazon-dynamodb/reviews)
  - [Amazon EC2](https://www.g2.com/products/amazon-ec2/reviews)
  - [Amazon Elastic Container Registry (ECR)](https://www.g2.com/products/amazon-elastic-container-registry-ecr/reviews)
  - [Amazon EventBridge](https://www.g2.com/products/amazon-eventbridge/reviews)
  - [Amazon Kinesis Data Streams](https://www.g2.com/products/aws-amazon-kinesis-data-streams/reviews)
  - [Amazon QuickSight](https://www.g2.com/products/amazon-quicksight/reviews)
  - [Amazon Relational Database Service (RDS)](https://www.g2.com/products/amazon-relational-database-service-rds/reviews)
  - [Amazon S3 Glacier](https://www.g2.com/products/amazon-s3-glacier/reviews)
  - [Amazon Simple Email Service (Amazon SES)](https://www.g2.com/products/amazon-simple-email-service-amazon-ses/reviews)
  - [Amazon Simple Notification Service (SNS)](https://www.g2.com/products/amazon-simple-notification-service-sns/reviews)
  - [Amazon Simple Queue Service (SQS)](https://www.g2.com/products/amazon-simple-queue-service-sqs/reviews)
  - [Amazon Simple Storage Service (S3)](https://www.g2.com/products/amazon-simple-storage-service-s3/reviews)
  - [Amazon Textract](https://www.g2.com/products/amazon-textract/reviews)
  - [AWS Amplify](https://www.g2.com/products/aws-amplify/reviews)
  - [AWS Batch](https://www.g2.com/products/aws-batch/reviews)
  - [AWS Glue](https://www.g2.com/products/aws-glue/reviews)
  - [AWS IoT](https://www.g2.com/products/aws-iot/reviews)
  - [AWS Step Functions](https://www.g2.com/products/aws-step-functions/reviews)
  - [Azure Ai Foundry](https://www.g2.com/products/azure-ai-foundry/reviews)
  - [Cargo Operations Management System](https://www.g2.com/products/cargo-operations-management-system/reviews)
  - [Coralogix](https://www.g2.com/products/coralogix/reviews)
  - [Datadog](https://www.g2.com/products/datadog/reviews)
  - [Docker](https://www.g2.com/products/docker-inc-docker/reviews)
  - [Elastic Stack](https://www.g2.com/products/elastic-stack/reviews)
  - [Google Analytics](https://www.g2.com/products/google-analytics/reviews)
  - [machine-learning in Python](https://www.g2.com/products/machine-learning-in-python/reviews)
  - [Okta](https://www.g2.com/products/okta/reviews)
  - [Oracle Database](https://www.g2.com/products/oracle-database/reviews)
  - [PagerDuty](https://www.g2.com/products/pagerduty/reviews)
  - [pandas python](https://www.g2.com/products/pandas-python/reviews)
  - [Python](https://www.g2.com/products/python/reviews)
  - [python sql](https://www.g2.com/products/python-sql/reviews)
  - [Salesforce Agentforce](https://www.g2.com/products/salesforce-agentforce/reviews)
  - [Slack](https://www.g2.com/products/slack/reviews)
  - [Slack Connector for Jira](https://www.g2.com/products/slack-connector-for-jira/reviews)
  - [TensorFlow](https://www.g2.com/products/tensorflow/reviews)
  - [Windows 11](https://www.g2.com/products/windows-11/reviews)
  - [Xurrent IMR](https://www.g2.com/products/xurrent-imr/reviews)

## AWS Lambda Features
**Development**
- Application Deployment
- Development Tools
- Development Environment
- Language Support
- Testing

**Database**
- Database Management
- Analytics
- Auto Scaling
- Backup / Recovery
- Storage

**Infrastructure**
- Networking
- Virtual Machines
- Security

## Top AWS Lambda Alternatives
  - [DigitalOcean](https://www.g2.com/products/digitalocean/reviews) - 4.6/5.0 (738 reviews)
  - [Red Hat OpenShift](https://www.g2.com/products/red-hat-red-hat-openshift/reviews) - 4.5/5.0 (289 reviews)
  - [Google App Engine](https://www.g2.com/products/google-app-engine/reviews) - 4.1/5.0 (192 reviews)

