AWS Lambda Reviews

There a variety of use cases for this solution but it is mostly used for data processing type transformations from one source to a target. In instances when Lambda works well, we are planning to increase usage. 

Deployment and maintenance of Lambda requires two people but this may increase depending on the size of the deployment.

Lambda has improved our organization by making it possible to transform data.

Lambda has limitations on the amount of memory you can use and is not a good solution for long running processes. If the amount of data is reasonably small, it will run and transform successfully. If you have tons of data coming in, it stops working and you have to restart it.

The orchestration and coordination between different Lambdas could also be improved.

I have used this solution or a couple of years.

This is a fairly stable solution. 

This solution has some limitations on scalability due to the problem with coordination between the different Lambdas. Is it not very straightforward and you have to do a lot of testing.

The initial setup was fairly straightforward.

I would advise others to use it in those circumstances where it works well and to be aware of the problems with coordination and orchestration. Make sure that it doesn't have to process tons of data.

I would rate this solution a seven out of ten.

Our company uses the solution as a function engine to deploy triggered events for customers. We have a team of twelve developers and our deployments have 1,000 to 2,000 customers during peak times. 

The solution runs on the latest cloud technology so it is easy to deploy cloud-native projects. 

The solution is very useful for managing triggered events. 

It can be a bit difficult to switch between accounts when creating services for customers. 

I have been using the solution for one year. 

The solution is cloud-based so of course it is stable as long as the cloud is available. 

The solution is scalable. 

We have not needed technical support. We utilize available documents that contain content for solving any issues. 

The solution is serverless computing so there is no setup. You just launch the service, write your code, and run it. 

The solution is part of the AWS subscription model that is paid annually. There is no charge for monthly usage. 

There are many calculation criteria for AWS services or licenses. It is difficult to say whether the solution reasonably priced or expensive. Each company weighs price against the benefits and efficiencies provided by the solution. 

AWS is the pioneer of cloud computing and they lead the industry in innovations. Other providers follow in AWS' footsteps to implement similar features and service levels. 

AWS has differentiated the use cases for serverless computing. Lambda is used for basic capabilities like triggered events and Fargate is used for extended capabilities. 

I started using Lambda for a specific use case and I continue to use Lambda and Fargate for use cases as recommended by AWS. 

I definitely recommend the solution and rate it a ten out of ten. 

AWS Lambda's most valuable feature is serverless architecture.

There are sometimes issues following an update.

I've been using AWS Lambda for about five years. 

AWS Lambda is stable.

AWS Lambda is scalable.

The initial setup was straightforward and took only a few minutes.

AWS Lambda's cloud version isn't expensive, and I'd rate its pricing as five out of five.

I would rate AWS Lambda ten out of ten.

Lambda makes the administration of all our services related to Amazon really easy. 

The metrics and reporting for this solution could be improved. 

I have been using this solution since 2017. 

From a stability perspective, I would rate it a seven out of ten. There is some room for improvement when it comes to stability of the features. 

This is a scalable solution. I would rate it a nine out of ten in this regard. 

The initial setup is complex. 

I would recommend this solution to others. Overall, the solution has improved since we started using it in 2017. 

I would rate this solution a nine out of ten.

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.

I am using AWS Lambda for building web and mobile applications.

AWS Lambda has helped my organization by making it easier to code and it is less costly.

The valuable feature of AWS Lambda is the ease of coding. It is easier to code using the solution.

AWS Lambda can improve its file system-based sharing capabilities and restrictions.

I have been using AWS Lambda for approximately six years.

AWS Lambda is stable.

The scalability of AWS Lambda is good.

We have approximately 1.3 million users using the application that uses the solution. We have 10,000 to 20,000 new users added every month.

The support from AWS Lambda is good.

I rate the support from AWS Lambda a four out of five.

The initial setup of AWS Lambda is easy. The full implementation took us there to four months.

I rate the setup of AWS Lambda a four out of five.

We did the implementation of AWS Lambda in-house.

We migrated from an on-premise server to the cloud with the Lamda solution and we found it less than one-10th of the cost of what it used to be. We have 90 percent savings.

I rate the ROI of AWS Lambda a four out of five.

AWS Lambda license is paid on a monthly basis.

I rate the price of AWS Lambda a four out of five.

My advice to new users is I would recommend strongly going with AWS Lambda for all API-based solutions.

I rate AWS Lambda an eight out of 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.

We have a DNS as a service and NAS as a service, which integrates, and we use Lambda functions there. We have a lot of applications that we use Lambda for. 

This solution is cloud-based. 

Some of the most valuable features are that it's easy to install and use. The performance is also good. 

Lambda could be improved in the sense that some of the things done with Lambda function take some time. So the performance could be better and faster. 

I have been using Lambda for many years. 

This solution is stable. 

This solution is scalable. 

I think, eventually, we will increase our usage. We need to move some of our services to Lambda. 

Amazon's technical support is good. 

Before implementing Lambda, we had legacy types of solutions. 

The installation could be faster, but I believe it's a straightforward process. I manage a team that handles the installation, so I can't comment on the specifics of the installation process. Within the team that handles maintenance and deployment, we have two engineers. 

We implemented this solution through an in-house team. 

We don't need to pay for licensing to use Lambda. 

I rate AWS Lambda an eight out of ten. I would recommend AWS Lambda to others. We provide a lot of services, part of which is that we write Lambda functions. 

We are primarily using AWS Lambda for real-time API services. We use AWS Redshift to support our Lambda code functions. 

This solution is cloud-based. 

One of the most valuable features of AWS Lambda is the performance. Lambda is very technical and has very high performance, as well as good real-time performance. 

AWS Lambda could be improved with better stability. 

I have been using AWS Lambda for more than two years. 

This solution is very, very stable. 

In our organization, there are around 300 users of AWS Lambda. We have plans to increase our usage. 

I have contacted Amazon's technical support, and they were very excellent. 

The installation is straightforward. The process took us under three hours, and we did it ourselves. For deployment and maintenance, we have a team of 10 engineers and developers. 

We implemented this solution through an in-house team. 

For licensing, we pay a yearly subscription. 

I rate AWS Lambda a nine out of ten. To those looking to implement AWS Lambda, I would recommend this solution, and say that Lambda has a learning curve in order to enhance the service when using it for the first time. I would advise the user to study hard to use Lambda as a tool.