AWS Lambda Reviews

Essentially, I use AWS Lambda to run Python code. Usually, I set up triggers for other parts of AWS. It's really basic programming tasks.

AWS Lambda is more integrable than other code software, which is a significant advantage. Given my software development experience, I find its integration with the cloud easier than with other platforms. There haven't been any problems while using it during my three-month internship.

A very minor improvement would be to simplify the instructions on setting a trigger, as I had to read through them multiple times at the start.

I have used AWS Lambda for three months.

AWS Lambda is entirely stable. I never encountered any issues while using it.

I haven't used it extensively, however, it seems scalable. During my internship, scalability hasn't been critical to what I've used it for.

I have never needed to communicate with technical support for AWS Lambda.

Positive

The initial setup was extremely easy. AWS Lambda is significantly easier compared to other IDEs or Visual Studio Code.

There is no specific advice I can provide at the moment because I've only done a short internship. Overall, I would rate AWS Lambda a ten out of ten.

We have used Lambda for

batch processing for specific schedules.

different bot functions that run regularly,

Application business logic

Easy to impliment without any environment provisioning

 The initial setup is straightforward. 

The stability is good.

It has good monitoring. the visibility is great.

From a very high-level perspective, it is a good solution, however, there are certain limitations. This becomes challenging for us. Specifically, a limitation is Lambda cannot continuously execute for more than 15 minutes. That could be one limitation. On an implementation level, there are certain limitations that I know about yet would not be the best person to explain as I am not technical.

The execution timeout can be increased so that if we have a lengthy process, it will not fail before their timeouts. We've had to revamp the way that it works due to that 15-minute timeout limitation.

We've been using over 2 years

It's very stable, and it's easy to monitor. They have all the required logs and dashboards available on AWS to see the progress. The visibility of it also is good when a Lambda runs and completes.

I would not say it's scalable in terms of usage. As the demands increase it is scalable. But if the lambda need more time to process it's not scalable beyond 15 mts.

I've never dealt with technical support. I can't comment on their services. 

Positive

It seems to be a straightforward process. However, I'm not directly totally involved with the Lambda implementation.

We are implementors and can set up the solution for clients. 

The ROI is very good. It's a positive thing as there's no investment at all. It's purely on usage you have to pay. There's no upfront investment required, and it's only on the requirement that you have to choose Lambda. With the cost not being very big, the ROI is very good.

The cost is based on the number of Lambdas used if I'm not mistaken. It's only a usage charge, not a license charge.

We are an extensively using

I'd recommend the solution to other users and organizations. 

With time-out limitation, it's not a perfect fit for the batch process which takes more than 10 min.

AWS Lambda needs to improve its stability. 

I have been using the solution for a couple of months. 

I would rate AWS Lambda an eight out of ten. 

The solution is scalable. I would rate it around eight out of ten. 

AWS Lambda is cheap. 

I would rate the tool an eight out of ten. 

We are building a Twitter-like application in the boot camp. I have used Lamda for the integration of the post-confirmation page in the application. This will help you get your one-time password via mail. You can log in with the help of a post-confirmation page. We didn’t want to set up an instance specifically for confirmation. We used the Lambda function so that it goes back to sleep after pushing up.

The tool changes its UI every month which is very frustrating for me. I don’t know why AWS keeps changing the UI. They can’t stick to a specific one.

I have not faced any stability issues with the tool.

I know that AWS has flexible support but if I encounter any problem, then I just Google it. I get a lot of support from Google, YouTube videos, and Discord channels.

The solution’s initial setup was neither easy nor complex. I started learning about cloud services about six to seven months ago and already had a background in it. However, the implementation was not easy since a lot of errors just popped up. I had to check the CloudWatch logs and look into the bugs in the code. It wasn’t interesting. The deployment took around two hours to complete.

I would rate the solution a ten out of ten. The solution works fine for us and we didn’t require the need to maintain it. I didn’t face any problems working with the product.

We're using AWS Lambda to trigger jobs and receive SQS messages. We're also using the tool as a single unit where you have computing, storage, and network.

AWS Lambda has improved my company through its usage in a distributed system, particularly event-driven architecture. When an event is passed to AWS Lambda from Amazon SQS asynchronously, the tool can call an ETL job, and it can trigger that job, and that job can trigger an AWS Lambda function, which can then send a message to the queue to complete the entire use case.

The most valuable feature of AWS Lambda is that you can trigger and run jobs instantly, and after you complete the job, that function is either destroyed or stopped.

The feature to attach external storage, such as an S3 or elastic storage, must be added to AWS Lambda. This is its area for improvement.

I've been using AWS Lambda for two years.

Stability-wise, AWS Lambda is an eight out of ten.

Scalability-wise, AWS Lambda is an eight out of ten.

I have not encountered any problems with AWS Lambda, so I didn't need to contact its technical support team.

We didn't use a different solution apart from AWS Lambda.

The initial setup for AWS Lambda was straightforward.

I saw ROI from AWS Lambda.

Price-wise, AWS Lambda is a five out of ten.

One person is enough for maintenance for a cloud-based tool, such as AWS Lambda.

I cannot share the number of AWS Lambda direct users in my company, as that figure is confidential.

My advice to others looking into implementing the tool is that it's easy to use as long as you know the basics.

AWS Lambda has good features, so I'm giving it an eight out of ten.

Our primary use case for the solution is automation. There was a scenario where we tried to reduce cost in our environment using Instance Scheduler, where the AWS Lambda function was also used during that process. So we use it for automation and tagging.

The solution has helped our organization with cost optimization. So we have used AWS Lambda for consolidated billing.

The automation feature is valuable.

The runtime for the solution can be improved.

We have been using the solution for approximately two years.

The solution is stable. I rate it a nine out of ten.

The solution is scalable, and I rate it a ten out of ten.

The initial setup was straightforward.

The solution is very expensive.

I rate the solution a nine 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. 

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.