AWS Lambda Reviews

Lambda is essentially a serverless computing service offered by AWS. It allows you to run your code or applications without needing to manage servers. You can deploy your IT code or applications, and it seamlessly integrates with other AWS services, like S3 for data storage. You don't need to purchase or manage any servers. So, Lambda offers a way to run applications without the complexity of infrastructure.

The best feature of AWS Lambda is its scalability and security. It's a highly scalable service, making it suitable for a range of applications.  

AWS Lambda, like other services offered by AWS, SAP, or Azure, is already quite advanced. However, when considering improvements, it's more about how you write and optimize your applications.

There's always room for enhancement in terms of resource allocation and management for high-demand applications.

Performance issues can arise depending on how you allocate resources within Lambda. For example, if you're running a new application with a significant load, you need to be prepared for potential bottlenecks. 

It's essential to control network interactions and optimize for the type of application you're running. Lambda is excellent for small and lightweight applications, but for more resource-intensive tasks, you might need to look at other AWS services or a more distributed storage environment.

AWS Lambda could greatly benefit from enhancements in handling large-scale applications to support heavy workloads. This is actually feasible, but there is a need for further development in this area. 

Additionally, improvements in resource control optimization are crucial. For instance, enabling users to run data-intensive applications using a limited number of resources without compromising performance would be a valuable addition.

I have used it for three years.

I have interacted with the AWS support team. They have a large customer base, which sometimes leads to delays, but overall, their support is excellent.

They categorize issues effectively and provide prompt support for critical issues. Even for less critical issues from the customer's perspective, their response is adequate. They are usually quick to respond, especially when the issue is critical, and they provide effective support.

The initial setup of AWS Lambda is very straightforward and quick.

If you have a data application with a huge number of users that requires frequent user interaction, AWS Lambda may not be the best fit. However, it's suitable for applications with less frequent user interaction, like those accessed periodically, maybe every few minutes or hours.

For lightweight applications, AWS Lambda is a ten out of ten.

We use it primarily for image resizing in batch and scheduled jobs. Additionally, one of our clients relies on Lambda for running a continuously active custom API, handling their ongoing API requests.

Leveraging it to run containers directly from Amazon Elastic Container Registry has proven to be highly valuable. The utilization of containers is particularly beneficial in overcoming the size limitations imposed on Lambda functions which not only allows us to work around these constraints but also contributes to the improvement and maintenance of our code.

There's room for improvement in the testing setup. Attempting to test it through the AWS CLI also posed issues, and when trying to test the Lambda function on my local machine, I encountered difficulties in obtaining comprehensive logs or error messages to diagnose what might be going wrong.

I have been working with it for one year.

It provides a high level of stability, and I have not encountered any issues so far. The system demonstrated stability whenever we attempted to update the function or perform any operations. Responses consistently aligned with the timeframes specified on the AWS website, remaining within the service level agreement. I would rate it nine out of ten.

The scalability is notably high, I would rate it nine out of ten. Approximately sixty percent of my clients are utilizing this approach. While I serve two major organizations, the majority of my clientele consists of small and medium-sized businesses.

The technical support from Amazon has been excellent, and I've consistently had positive experiences. During a customer migration from another cloud provider to AWS, the entire technical team provided valuable insights and enhanced the architecture. Their assistance not only improved the overall design but also ensured smooth transition and support. Even for minor issues, the response times have consistently exceeded the expectations stated on the website. For instance, if a 24-hour response time is indicated, they typically respond within twelve hours. I would rate it nine out of ten.

Positive

I would rate the initial setup around seven out of ten. While it wasn't overly challenging, it did demand a certain level of technical proficiency. Someone without substantial technical knowledge might find it less straightforward to set up.

In our container-based approach, we initiated by constructing containers on the local developer machine, then we pushed these containers to AWS Elastic Container Repository. Following this, we established a Lambda function that utilized the uploaded ECR image, allowing it to execute the associated container. Additionally, we incrementally built services to utilize those containers at Lambda functions. The deployment took less than three hours.

The pricing varies based on the specific solution you're implementing, and in comparison to the value it provides, the overall cost is reasonable. When used appropriately for its intended purpose, the price is relatively low. However, if Lambda is employed outside its intended scope, the cost can escalate exponentially. I would rate it four out of ten.

I recommend thoroughly reading the documentation to determine if it is a suitable solution for your specific use case. It's essential to understand the nuances of your use case before proceeding with the implementation. Overall, I would rate it eight out of ten.

We are building microservices in Lambda and exposing them via an API Gateway for the end consumer. These microservices talk to DynamoDB, or third-party APIs but can also be event-driven. These microservices carry out specific business functionalities.

We have plans to increase usage in the future. We have been modernizing our usage of SOA technology and rewriting those SOA services on the cloud using AWS Lambda. We are transitioning to a serverless environment using Lambda. 

Lambda is the preferred compute option because of on-demand cost. We don't have to provision any hardware beforehand. We don't have to provision the capacity required for the services because it is serverless. 

AWS takes care of things behind the scenes and we pay only for usage. We don't have to incur uptime or the upfront cost to procure a EC2 instance or create any ECS service.

You can trigger Lambda in various ways including API Gateway events or a S3 object event. You can create a file in SP and it can trigger a Lambda function. You can process the file based on the event and complete asynchronous programming. It supports both synchronous as well as asynchronous programming. It is integrated with variety of AWS services like the S3, SQS or SNS.

You can use Lambda for a variety of use cases. You just have to write a Lambda which can be in various languages including Python, Node.js or Java. There is no limit on what you can do with Lambda because it is integrated with a variety of AWS services. 

The first time Lambda is started up, it takes some time to spin up an instance for serving the consumer requests. AWS has been trying to solve this in a variety of ways but have not yet managed to do so. 

Lambda can only run for a maximum for 15 minutes. If you have a job which requires running for more than 15 minutes, you cannot use Lambda for that use case. 

I have been using this solution for five years. 

I would rate Lambda an eight out of ten for stability. 

This is a scalable solution. I would rate it an eight or nine. You can have 999 Lambda instances running at a particular second at one time. That is the default. It you need to scale above this, you can request for AWS to increase your capacity.

I would rate the technical support an eight out of ten. We do contact the AWS support team if we are stuck or something is not working. They provide their input and we set up a call with them to explain our issues and reach a resolution.

Positive

The initial setup is straightforward. They have variety of ways to set it up via the console, ETK or CFT. You can easily configure Lambda via variety of ways based on your experience. Usually, newcomers will use console which is a UI and makes your task easier. Experienced people will go with CLIs, SDPF or CFTs to create Lambda resources.

We are not just deploying Lambda. We have a variety of AWS services which we combine into one script and we do it via an AWS code pipeline.

I would rate the setup a nine out of ten.

Deployment was done in-house by our own team. The patching of underlying hardware and other maintenance is done by AWS. 

We have experienced a ROI using this solution. I would rate it an eight out of ten. 

Lambda is an affordable solution. They offer free requests every month and charge per the compute time. If you are working in a big organization, usually AWS offer a savings plan where you get approximately 70% discount on pricing.

If one is very affordable and ten is expensive, I would rate this solution a two out of ten. Costing is per account. Production will involve a higher cost. 

If you are planning to implement the solution using scripting language like Node.js or Python, it's better to rather use traditional programming language like Java, or .NET, because Lambda runs faster and more efficiently. We implement it using these scripting languages as the first choice.  

It is important to understand your use case properly and if Lambda is a good fit. Solutions such as Docker, Kubernetes, OpenShift or normal EC2 instances may be a better fit for your business.

I would rate this solution a nine out of ten. It integrates well with variety of AWS services which makes the event-based programming easy. Lambda is well suited to a variety of use cases or applications.

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.

I have found this solution very useful. By using Lambda, we can use Python code and the Boto3 solution. 

The triggering feature is also valuable. For example, if we are using Kafka, we need to be aware that the language comes in Kafka when we write in Python, and that we are transforming our data into the meaningful server and dumping that into the S3 bucket.

I would like to see a find and replace function as part of Lambda's future releases. Currently, if we want to replace a code, we copy the code into Notepad, then find and replace it, and then copy that to Lambda. This would improve the editing function of the product.

Lambda would benefit from a debugging feature as well. For example, if you want to debug code running in Python and deployed in Lambda, it would be beneficial to have a debugging feature.

I have been working with AWS Lambda for one year.

The solution is stable. There are times when we do need to refresh when we make changes and deploy them. This seldom occurs.

We have five developers using Lambda. 

Technical support can take a long time to respond. I would rate their service a seven out of 10.

Neutral

The initial setup of AWS Lambda is simple.

I would rate this solution a seven out of ten overall. 

I use AWS Lambda for event-driven computing and various other projects that benefit from its serverless architecture.

AWS Lambda supports event-driven computing, which is incredibly beneficial for our projects. Its scalability allows us to handle varying amounts of load efficiently, and it integrates smoothly with other AWS services to enhance our application workflows. 

Additionally, AWS Lambda is cost-effective, providing noticeable cost savings.

I would like to see improvements in AWS Lambda's stability and setup processes, as there were some complexities encountered initially.

I have been working with AWS Lambda for a substantial amount of time.

We have faced some stability issues with AWS Lambda, although it generally performs well.

AWS Lambda is scalable, and we have found its scalability beneficial for our projects.

I have not escalated any significant issues to customer support regarding AWS Lambda, but generally, AWS support is helpful.

Positive

I have experience with other compute services from different vendors, such as Azure.

The initial setup of AWS Lambda was somewhat complex and not entirely straightforward.

AWS Lambda has contributed to cost savings and performance improvements in our organization.

The pricing of AWS Lambda is reasonable, though there is always room for more flexibility.

I have evaluated solutions from other vendors, including Google and Microsoft Azure.

Overall, I would recommend AWS Lambda to others due to its capabilities. On a scale of one to ten, I would rate it quite high - and eight.

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.

Our primary use case for AWS Lambda is a backend service module. Thanks to this solution, we do not need to worry about hardware or resource utilization. It saves us time. 

It saves us a lot of setup time. And, because it's our code, we will use Lambda. Lambda is the best AWS product we can use for running our code and it is very quick for the developers. All they have to do is commit their codes and, once we set up our code pipeline once after committing the code and building and deploying to our Lambda, the project will be up and running in the market. This setup is better than managing on EC2. We don't need to use EC2 in this case. 

My opinion is that the integration could be improved in this solution. We have had some difficulties integrating the EC2 module, but we found a solution for that by ourselves. I would say the integration needs to be improved.

I have been using AWS Lambda for about three years.

This solution is very stable.

My impression is that this solution is 100% scalable. The Lambda function is the most powerful product that the developer needs. 

We have one Lambda used by 50 to 100 people, and then we have another Lambda method that could be used by thousands.

My impression is that the setup was quite straightforward.

Overall, I would rate this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best. I would definitely recommend this solution to other people.