AWS Lambda Reviews

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.

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.

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.

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.

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

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.

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.

The cold start latency can be a challenge, especially for latency-sensitive automation tasks that aren't invoked frequently.

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.

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.

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.

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

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.

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.

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

AWS Lambda removes the need for server maintenance, which makes deployment simpler and faster.

.Very good for automation and security using python

Nothing i think because it’s have anything needed

Less work, lower cost, and faster development

I like that AWS Lambda is flexible and on-demand, allowing for computing without worrying about persistence. It scales horizontally and handles workload on-demand, so I don't have to anticipate demand like with traditional servers. Also, the initial setup was pretty easy, although it does require a little knowledge of compute and hardware.

It's expensive and the 15 minute timeout is hard sometimes.

AWS Lambda allows me to compute on-demand without persistence concerns, offering greater flexibility than EC2. It handles workload spikes without needing to anticipate demand as we would with traditional servers, and I appreciate its on-demand scaling.

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.

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.

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.

Analyze and transform continuous data streams.

Applications are restricted by strict, hard limits on memory.

It speeds up deployment by letting developers focus only on the code instead of the surrounding infrastructure, which helps shorten time-to-market.