AWS Lambda Reviews

There's a lot of use cases. The solution is used for immediate processing, so it's used everywhere. When data comes in, you process a Lambda function to tag it and categorize it. I've used Lambda functions to process inbound videos to make them smaller. I've used a Lambda function as a serverless backend for a customer-facing app, so I didn't have servers running.

With a highly variable load, our idle cost is pretty much zero, and we haven't had any scale barriers, so we've scaled smoothly.

I think the most valuable features are event-based triggers. Basically, a Lambda function doesn't get called because you say, "I'm going to call it." It gets called because something happens: a file arrives, a message arrives, or a database gets written. It's really good for a reactive style when you want things to happen as soon as something else happens. That's the best pattern.

There's room for improvement in the solution's warm start, which refers to the minimum time it takes to start up a Lambda function if you haven't been running it. 

I have been using Lambda since 2014, so about eight years. 

This is a stable solution. 

This solution is scalable. We have hundreds of thousands of users, so everything in Lambda gets used a little bit at a time in different parts of the process. We have plans to increase our usage in the future. 

I would rate the technical support as a ten out of ten. You are able to pick a language, pick an environment, and deploy it. 

It is pretty straightforward to set up this solution. 

We've run some scenarios. For example, say you have three million requests per month, and 120 milliseconds each time someone requests. The total cost ends up being $2.73 a month, which is very cheap for what you get.

There's two charges for this solution. There's the charge for how many times you call a Lambda function, which is 20 cents for every million function calls. Then there's also the size and amount of time that the Lambda function runs, which is measured as 0.0000166667 dollars. It's a fraction of a penny for every gigabyte second. A gigabyte, if you ran it for like a million seconds, would cost one dollar. It computes by the cycle, and it's very cheap.

My advice is to think about the architecture first and don’t just throw your code into Lambda. Think about how your application is designed because using serverless is different.

I would rate this solution as a ten out of ten. It's a very critical service. 

Public Cloud

Amazon Web Services (AWS)

AWS Lambda is a serverless computing service provided by AWS. It is allowed to run the course without the provisioning or managing server and paying only for the compute time consumed during execution.

The most valuable features of AWS Lambda are a serverless and event-driven architecture. The solution provides automatic scaling and supports languages like Node.js, Python, and Java.

AWS Lambda should support additional languages.

I have been using AWS Lambda for two years.

AWS Lambda is a stable solution.

More than five people are using the solution in our organization.

The solution’s technical support is good.

The solution’s initial setup is easy.

AWS Lambda is a cheap solution. The solution has a generic pricing before being triggered. After triggering, we need to pay the bill based on how much time the server runs.

Our company decided to use AWS Lambda because it is integrated with AWS services. The solution enables the building of serverless applications and provides automatic scaling and event-driven execution. AWS Lambda can be triggered by various AWS services like AWS S3, DynamoDB, AWS API gateway, and AWS CloudWatch.

I would recommend the solution to other users. It is easy for someone to learn to use Lambda for the first time.

Overall, I rate the solution ten out of ten.

Public Cloud

Amazon Web Services (AWS)

I have to send daily reports. We have many child accounts in AWS Organizations. We need reports on the cost of the accounts. I use AWS Lambda because we have to run the code without provisioning the servers. AWS Lambda is a serverless computing service.

The tool scales automatically based on the number of incoming requests. It supports multiple languages. We can use Python, Java, and Ruby. We can use the solution to stop and start the instances.

We must at least know the basics of languages like Python or Java to implement automatic processes and daily schedules. We must learn the Lambda function and the languages to use the tool.

I have been using the solution for three months.

I rate the tool’s stability a nine out of ten.

I rate the scalability an eight out of ten. We have more than 100 users.

The support team does not know how to implement and build the solution.

Neutral

We must know Python or Java to implement the product. It is not easy, but it is not difficult. We need some experience.

We only need to pay for the compute time our code consumes. The solution does not cost much.

I will recommend the product to others. We can automate the processes and integrate the solution with other services. The product provides elasticity and automatic scaling features. Overall, I rate the product a nine out of ten.

We have one or two use cases for real-time file processing. We use the event triggers to detect file arrival.

AWS Lambda is serverless. It is quick to deploy. The event-driven execution model has improved the project efficiency because it is quick and easy to deploy. However, it also introduced a set of new problems. It is the industry traction ever since the network went fully API.

Since the tool is serverless and it is hosted in the cloud, we do not need an initial capital investment on servers. We can pay as we use. We have integrated the product with other AWS services. We use SNS and SQL. There is an offering from AWS for integrated solutions.

We face some problems with the event-driven execution model.

The tool is very stable. There are certain things that we have to do to support it, but once we cross the t's and dot the i’s, it works.

The initial setup seems to be very straightforward.

I will recommend the solution to others for serverless computing needs. It’s a quick delivery. We do not have to set up servers before we start deploying. Overall, I rate the product a nine out of ten.

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.

Positive

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.

Public Cloud

Amazon Web Services (AWS)

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.

Public Cloud

Amazon Web Services (AWS)

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.

Public Cloud

Amazon Web Services (AWS)

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.

Public Cloud

Amazon Web Services (AWS)

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. 

Public Cloud

I use AWS Lambda for serverless computing, and I am charged only for the AWS Lambda instances I use. I value its cost efficiency because it activates instances based on load and tasks initiated.

I appreciate AWS Lambda for its serverless computing, with charges incurred only for the used instances. This serverless architecture enables the activation of instances based on task load, contributing significantly to cost efficiency.

Currently, I don't have any specific suggestions for improvements. However, enhancements could be introduced to better satisfy customer requirements.

I have used AWS Lambda for around two years.

The initial setup of AWS Lambda is quite straightforward and easy.

I rate the stability of AWS Lambda as a ten out of ten, suggesting that it is highly stable.

I rate the scalability of AWS Lambda as eight out of ten. Although it is stable and scalable, the number of instances can be optimized for other workloads when needed.

I rate AWS Lambda's technical support an eight out of ten. The support can be improved by increasing the number of support personnel.

Positive

The initial setup of AWS Lambda is quite easy.

The pricing of AWS Lambda is reasonable. It's beneficial and cost-effective for users regardless of the number of instances used.

I recommend Amazon Web Services Lambda to other users. I rate AWS Lambda as one of the best solutions, giving it a ten out of ten overall.

Public Cloud

Amazon Web Services (AWS)