AWS Lambda Reviews

We use AWS Lambda for jobs that we just want to offload to a cloud function. We are an educational institution, and if I want to upload an exam I generated for all my students, then I just write the script on AWS Lambda. That is, we use it for independent jobs that we can offload on their own.

I like the pay-for-what-you-use feature. This is the main reason why we use AWS Lambda. I don't have to manage servers; I just have to configure Lambda and expose it to an API gateway.

AWS Lambda's cold start needs to be improved. It has to warm up first, and so, the response time is slower.

Another challenge I've noticed is that there is a limit to the environment variables such as the 4 KB limit. Although, the advice is to use parameters or other things to store the details when the limit has exceeded the data, this adds additional intensity to the application. If the size limits for environment variables can be revealed, it would be helpful. Even if we have to pay for it, at least we would know that we are not dealing with latency. So, I would like to see the size of the environment variables increased.

I've been using AWS Lambda for one year.

It's very stable.

AWS Lambda is scalable; I don't need to worry about it. At present, we have less than 10 people using this solution.

The initial setup is straightforward. It can be done on the console, and you can use the infrastructure as the code.

The deployment time can vary from 10 minutes to an hour depending on your needs and how comfortable you are with AWS Lambda.

AWS Lambda now supports multiple languages, but find out if the language you want to use to write your jobs is supported by it. If it is supported, then you are good to go.

Because AWS Lambda is scalable and does what it's meant to do, I would rate it at nine on a scale from one to ten.

AWS Lambda's best features are log analysis and event triggering and actioning.

AWS Lambda's GUI could be improved with a twist or tweak in its look and feel to make it more impressive.

AWS Lambda is reliable.

AWS's technical support is amazing - they can turn a case around in a single email.

The initial setup is straightforward as Lambda is a built-in feature of AWS services.

AWS Lambda is phenomenal with data, and I would rate it nine out of ten.

AWS Lambda is used to write developer codes in Python. It is a place we can run where we can run our codes.

AWS Lambda is interlinked with CloudWatch. When we have any errors we can directly go there and check the CloudWatch logs. Additionally, we can run it very fast and we can increase the RAM size and other components.

We don't have the inbuilt modules in AWS Lambda. If more modules were built into or integrated with AWS Lambda, that would help developers to code.

I have been using AWS Lambda for approximately two and a half years.

The solution is stable.

The scalability of AWS Lambda needs to improve.

We have more than 100 users using this solution in my organization.

I have not used the technical support from AWS Lambda.

I have not used other solutions prior to AWS Lambda.

AWS Lambda is a very inexpensive solution. They charge for the number of times we run it. If you run AWS Lambda for one time, they charge around 50 cents or 25 cents for the use. I don't know the exact price, but it's less than a dollar.

AWS Lambda is user-friendly, people can learn very fast. People should start using AWS Lambda instead of using their own servers. It is very cheap and is the best way where any student can learn.

I rate AWS Lambda an eight out of ten.

My primary use case for this solution is usually for event-driven architecture. Since it's AWS, it's cloud-based. 

I have found all of the features valuable. It's an easy and cheap solution. 

AWS Lambda could be improved by increasing the size of the payload. Also, sometimes Lambda doesn't implement well for bigger solutions. 

I have been using this solution for three years. 

This solution is stable. 

I would rate customer support a nine out of ten. I have made three or four service requests and those were all resolved within 24 hours. 

I didn't use a different solution before implementing Lambda. 

The installation is straightforward. There isn't really anything you need to do. If you know exactly what you want, it can be done in five minutes. 

I implemented this solution myself. 

I pay for a monthly license. The licensing options will depend on the users. There's a monthly option and a yearly option. 

Lambda is a good and cheap solution and I would recommend it to those without a huge payload. There are around twenty or thirty people using Lambda in my organization. 

I would rate this solution an eight out of ten. 

Lambda can be used for automating AWS resources. 

It can also be used for automation outside of the cloud and for serverless applications. With Lambda, you can apply the code directly. 

The stability of the solution is very good, as is the performance.

It's a brilliant Amazon service that provides for many use cases. It's quite flexible.

The product has been very easy to use. All you have to do is configure a Lambda function and then deploy your code directly there and then you can invoke it in different ways. 

It is easy to configure.

The initial setup is very straightforward. 

Technical support has been great in general.

It would be ideal if we could use the solution across different platforms.

The integration could be better.

I've been using the solution for three years at this point. 

The solution is stable and the performance is great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

We have multiple applications. Most of our applications are Lambda-based, I would say there are around a hundred at this point.

The technical support on offer is brilliant. There shouldn't be any concern with contacting them. they are helpful and responsive. We are satisfied with the level of service on offer from them.

We have found that the solution is easy to install. You just have to do it through the UI and you can easily configure it and deploy it directly.

For deployment, et cetera, we just need one cloud ops engineer per day.

I was able to handle the implementation myself. I did not need the assistance of any consultants or integrators. Individual users should be okay if they want to install it themselves. 

We don't need to worry about monthly or yearly licenses. 

I'd rate the solution at a nine out of ten. I've been very pleased with its capabilities in general.

I would recommend the solution to other users and companies. 

We primarily use the solution for our backup coding for one of the ABDI services. We had a big job for the callout function, therefore we implemented Lambda here.

Lambda is the function we need to deploy any code.

We like that we don't require any infrastructure for it, which allows us a lot of cost savings.  

The solution has the capability to scale.

The product is quite stable.

The initial setup is pretty straightforward.

We've found the technical support to be very helpful.

It's a fairly easy solution to learn.

I can't recall any features that might be lacking. For us, it works quite well, however, it depends on what a company needs.

We'd love to see more integration potential in the future.

I've been using the solution for about two years at this point.

The solution has proven to be very reliable and quite stable. The performance is good. There are no bugs or glitches and it doesn't crash or freeze on us. 

The product scales well. If a company needs to expand, it should be possible to do so.

We have more than 5,000 users on the solution currently.

Technical support from Amazon is excellent. They are extremely helpful and we find they respond quickly. We're very happy with the level of support we receive. 

The initial setup is pretty straightforward. It's not overly difficult by any means. Ashish:
The Lambda function is not that hard to set up due to the fact that we generally go to the AWS services URL and we can easily find the Lambda function from there.

The solution really doesn't require that much maintenance. You don't need a big team on it at all.

The solution is fairly reasonable, and, as it doesn't require any infrastructure, can save a company a lot of money simply by being on the cloud.

We bought a license from AWS that renews yearly.

We're using the latest version of the solution. It automatically updates as it is based on the cloud.

I'd rate the solution at a nine out of ten. We are quite happy with its overall capabilities.

I'd recommend the solution to other users and other organizations. It's very easy to learn.

The primary use case is processing data. We use the pipeline multiple places to process the data. Whatever JSON files we get, we have to standardize, enrich, and also format to the application.

The most valuable feature is that it's serverless. Therefore, server configuration is not required, and we can run it directly anywhere. We can write Java code or Python code in that.

The initial setup is straightforward as well.

AWS Lambda is good for short-term automation processes.

If you want to run processing data, which takes less than 15 minutes, then you can use Lambda. However, if it is a specific ETL process or a long-term one, then AWS Lambda is not a good option.

The longer Lambda runs, the higher is the cost incurred because the cost is based on runtime.

At times, it hard to know when Lambda should be used and when it should not. So in the future, if there are serverless extensions, it would be fine.

I've been working with AWS Lambda for six to seven months.

The initial setup of AWS Lambda is straightforward.

The cost of AWS Lambda is based on runtime.

It's a good product, and we use Lambda for short run processes, for example, processing a file from the landing zone. Suppose FTP or SFTP has put a file in one landing area, and we have to push a file to the S3 bucket. We would not need to do any writing, shell scripting, or Linux coding, etc. In general, with Lambda you can get the Python coder or Java code.

So, professionals can easily perform these tasks within a short time. This will help with agile processes and sprints. My advice is that AWS Lambda is a good service for short-term automation processes.

I would rate AWS Lambda at eight on a scale from one to ten.

AWS Lambda enables server-less architecture for seamless orchestration. We use the solution for various orchestrations. This is very useful when you would need to perform orchestrations of the different applications together. Many organisations are using this solution for web and mobile applications at scale. 

The main features of this solution are the ability to integrate multiple AWS applications or external applications very quickly and organize all of them by leveraging server-less computing power of AWS. Additionally, it is easy to use and you can run various programming languages, such as Python, Go, and Java.

There is room for improvement in user-friendliness. When comparing this solution to others it is not as user-friendly.

We have been using this solution for over five years for various server-less computing on AWS. My current employer has pioneered on this technology and serving various global clients for years. 

This solution is a serverless architecture in which you do not have to manage any infrastructure which makes it very stable.

The solution is highly scalable. 

We have plans to increase usage because most of the workload and applications are using this solution.

The technical support is managed by AWS which is good.

Azure Logic App & Function App, Google Pub-Sub etc. 

Managed by AWS

The price of the solution is reasonable and it is a pay-per-use model. It is very good for cost optimization.

I would recommend this solution to others. If you are with AWS it is better to use the serverless architecture.

I would rate AWS Lambda a nine out of ten.