AWS Lambda Reviews & Product Details

Awesome service if you are looking for some quick quirks!! I would recommend highly if you are looking for running serverless applications which can also integrates with many AWS services like S3, DynamoDB, API gateway etc. The best thing about this service is automating things with ease and you pay only for the compute time you use. Review collected by and hosted on G2.com.

Only disadvantage over this many advantages.. Need to perform some work around as the execution time is quite long (15 minutes). Debugging might be tricky some times as the logs are stored directly in CloudWatch and sometimes its quite difficult to debug. Review collected by and hosted on G2.com.

Its easy to setup with a small image and less code Review collected by and hosted on G2.com.

its not very user friendly and kron job setting is a bit hard Review collected by and hosted on G2.com.

Its best part is, pay as you use. It charges only it is called for any API call Review collected by and hosted on G2.com.

It Cannot be used for multiple API call, it can incur more cost Review collected by and hosted on G2.com.

One of the best things about AWS Lambda is its seamless integration with various AWS services like S3, CloudWatch for logging, and email services. Whenever my lambda function is not able to work properly, I can simply go to clouwatch and see the logs and it help me to understand the problem. And one more thing is that it is easy to create AWS lambda function. Review collected by and hosted on G2.com.

AWS Lambda has predefined limits on memory allocation (almost 10Gb)which make it not suitable for heavy workloads.

It is mostly used for the smaller product which need a less memory allocation. Review collected by and hosted on G2.com.

No dependancy on servers to run your code. Review collected by and hosted on G2.com.

Too many processes execution makes the use of Lambda limited and have many memory constraints. Review collected by and hosted on G2.com.

Can run code without managing server, as it provides server less architecture Review collected by and hosted on G2.com.

Sometimes takes too much time to execute Review collected by and hosted on G2.com.

It's a useful and flexible tool to run code on cloud without setting up servers Review collected by and hosted on G2.com.

It just does what it needs to do. Nothing wrong about it Review collected by and hosted on G2.com.

1. I personally rely too much on lambda functions whenever I need to automate a certain action based on some triggers which happens on daily basis. The trigger can be as simple as user clicking on a button on some UI or as complicated as getting webhook notifications from any third party website.

2. Despite AWS's other offerings like EC2, I prefer using Lambda because it is reuse a lambda function in different places of a project or any project as long as the input argument remains the same. Review collected by and hosted on G2.com.

1. At times the execution endup taking time.

2. I found it pretty intimidating for even the technical person to learn AWS Lambda and how it can be used to automate several operations and save time. Although there are help documentation one can refer to, to learn and setup their AWS functions. Review collected by and hosted on G2.com.

Serverless, scalable, event-driven, and integration abilities. Review collected by and hosted on G2.com.

Ramp-up time in learning is required for successful implementation and usage. Review collected by and hosted on G2.com.

What I like most about AWS Lambda is that it makes deploying code simple without needing to manage any servers. It scales up automatically when needed and only charges when your code is running, which helps keep costs under control. AWS Lambda also works well with other AWS services, making it really flexible for building event-driven applications. Review collected by and hosted on G2.com.

One of the challenges with Lambda is the "cold start" delay, which can slow things down a bit, especially if the function hasn’t been used in a while. Additionally, there’s a timeout limit that doesn’t work well with long-running tasks, so some processes have to be redesigned to fit within those limits. Lastly, costs can add up quickly with a high volume of requests, so it’s important to monitor usage. Review collected by and hosted on G2.com.