AWS Lambda Reviews & Product Details

I really enjoy the way Lambda is able to scale to your workloads without developers having to worry about it. Write less code and configurations with Lambda is amazing and helps move business objectives forward faster Review collected by and hosted on G2.com.

I would like to see the way Lambda handles dependencies change a little bit. If we could just pull in the libraries that i need rather than packaging them all together would be awesome Review collected by and hosted on G2.com.

I use lambda as often as I can for as many of the scripts that I used to need a running server for. It's great for collecting metrics on instances and deploying policies and what not. While I don't recommend it to everyone as it does take a bit of learning on top of the code that you write, it is a very useful tool that once you understand it, works very well. Review collected by and hosted on G2.com.

The lack of commonly used python modules like "requests" make it a bit more difficult as you have to go through extra steps to include them in the code. Review collected by and hosted on G2.com.

It's a great tool, for serverless architectures, the possibility of run code and gets charged only for the number of times you run the lambda function. Great for loosely coupled architectures Review collected by and hosted on G2.com.

There are no cons that I can mention right now, I've been using this service for a long time and it's amazing Review collected by and hosted on G2.com.

The thing i liked the best is the ease of usability and fast working capability. I can create my API's in minutes without considering any back-end resources all are been managed by AWS. The wrapping up of my code to a desired solution is very easy and with minimum guidance. i am glad to have AWS this awesome feature of lambda function. Review collected by and hosted on G2.com.

The thing which I do not like about AWS is, it do not give proper error report. many times i get stuck into the mid of logic and do not a way out, i get confused whether the error is of AWS or in the business logic which i wrote. Review collected by and hosted on G2.com.

Best thing I have found while I came to know about AWS lambda is - I can use any of my favorite programming language to develop the function and I also don't need to bother about environments.

It has various and all major trigger type available in AWS service e.g S3 and many more.

Even AWS toolkit also integrates with visual studio (my favorite IDE) to test & debug the lambda functions in C#.

Lambda functions can be triggered by - s3 object put/post/delete - all events, cloud watch event, aws code commit events. Review collected by and hosted on G2.com.

Sometimes the trigger on S3 events don't trigger the lambda functions.

Debugging setup is difficult when you are working on AWS lambda using AWS toolkit. Review collected by and hosted on G2.com.

For minimum requirement or simple API, it is the best thing to start with. Easy testing up with inbuilt functionality to test lambda function with custom input types. Major development language support like Python, nodes.js etc.

It has various and all major trigger type available in AWS service e.g S3 and many more.

The best cost-effective lambda function in the market.

Sometimes the trigger on s3 fails to invokes, particularly transcribe job. Review collected by and hosted on G2.com.

Dependencies and package management is a somewhat irritating process.

The first thing it requires custom python packages which are particularly compatible AWS Linux environment. Struggled a lot in the initial stage. Once created I think it should have remembered the dependencies.

Also, need to upload the whole package + code if the size is bigger need to upload via s3 bucket.

If the size increases the editor does not load up the code, so the development and testing cycle time increase with given into consideration that it needs to follow the whole process for uploading the package.

For the beginner, I guess the development support for video tutorial & detailed documentation could have been better.

Review collected by and hosted on G2.com.

AWS lambda is the cloud computing concept by which we can execute our code as function on cloud without worring about server management and it will cost us as per the method calling or number of times it has been called. This is the best for application which are based on cloud architecture. Review collected by and hosted on G2.com.

Sometimes our code is dependent on other software and in this case, we will not be able to implement this concept because to run the code we are using amazon services which is lamba. we don't have the control over its environment in which it is executing. If there is any way of doing that, then there are no cons of using it. Review collected by and hosted on G2.com.

Lambda is great for when you need something that *just works* without needing to manage underlying servers and infrastructure. The functions will exist 24/7. And furthermore you are only billed for the time that your function spends doing work for you. So there is 0% underutilization that may happen with traditional EC2 instances Review collected by and hosted on G2.com.

VPC Cold Starts, Especially with .NET based lambda functions can exceed several seconds, which is unacceptably long for many use-cases Review collected by and hosted on G2.com.

Lambda is extremely useful when we have a project of extension to our software that doesn't really belong with in any of the existing, larger code bases. It makes for a clean place to add the code without 'messing up' the main code base. Review collected by and hosted on G2.com.

We primarily use it for REST APIs, so the requirement to use API gateway ( which can be a bit of a pain) just for a very simple function seems un-necessary and time consuming Review collected by and hosted on G2.com.