AWS Lambda Reviews

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 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)

We use AWS Lambda for various tasks, such as triggering reports, queueing calls for displays on our dashboard, and integrating with environmental variables for different outputs.

AWS Lambda saves a lot of time in our project deployments by allowing us to create users, establish user policies, handle voice mail set-ups, and develop dashboards with live views of agent status and queue additions, thus enhancing overall efficiency and cost-effectiveness.

One of the really handy features is keeping the environment variables in the Lambda for our outputs. It makes configurations more convenient as changes can be made through the environmental variables without altering the main code.

One area of improvement is Lambda's runtime version management. It currently requires manual user maintenance to upgrade and evaluate, and an automated provision for this would be beneficial.

We have been using AWS Lambda for more than two years, starting from the deployment of Amazon Connect.

AWS Lambda is quite stable. However, any changes in versions may require small code adjustments, which we must manage.

AWS Lambda offers a high level of scalability. It can handle multiple calls automatically when busy and reduce to one when free. I rate it a nine for scalability.

AWS offers excellent technical support. They have been very helpful, especially when one of our Lambdas was not functioning due to a minor code discrepancy that required a simple fix.

Positive

The setup for AWS Lambda is quite easy. The challenge lies mostly in ensuring our code is error-free for successful execution.

AWS Lambda is very cost-effective. It allows for one hundred thousand requests for free per month, and subsequent requests incur a very low cost per trigger.

Ensure that you have foundational knowledge of cloud formations or other AWS services for an optimal experience with AWS Lambda.

I'll rate the solution ten out of ten.

Hybrid 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.

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.

AWS Lambda is used only by the DevOps team. I can use the solution to configure and set up all the requirements for testing the application and test code.

AWS Lambda should improve its compatibility with the language used to write the code. I would like to be able to choose a different language to code in AWS Lambda.

I have been using AWS Lambda for six months.

Around 15 to 20 users work with AWS Lambda in our organization. The solution is used by different teams, including the DevOps, testing, and development teams.

I faced some challenges when we worked on the migration. I raised tickets to the support team, and they helped me.

The solution's initial setup can be done with the help of documents.

AWS Lambda is not expensive for micro testing but is expensive if used for long deployment or long services.

It is not difficult for a beginner to learn to use AWS Lambda for the first time because it has good documentation.

Overall, I rate the solution a five out of ten.

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.

Public Cloud

Amazon Web Services (AWS)