We have two or three applications that are hosted with Lambda. Being on cloud, the solution has its own advantages with good management of resources. You can spin up anything instantly without any investment and disaster recovery or HA is taken care of by the service itself.
Chef manager at a insurance company with 5,001-10,000 employees
Excellent management of resources with good disaster recovery
Pros and Cons
- "You can spin up anything instantly without any investment."
- "Security needs to be improved."
What is most valuable?
What needs improvement?
I believe Lambda security needs to be improved.
For how long have I used the solution?
I've been using this solution for one year.
What do I think about the stability of the solution?
The solution is stable.
Buyer's Guide
AWS Lambda
December 2024
Learn what your peers think about AWS Lambda. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
How are customer service and support?
I'm satisfied with the technical support, they respond quickly.
How was the initial setup?
The initial setup was straightforward and we currently have four engineers working on the product.
What's my experience with pricing, setup cost, and licensing?
Licensing is on a monthly subscription model and is usage-based.
What other advice do I have?
I rate the solution nine out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Data engineer at Cocos pt
Does not need server configuration and can be used for short-term automation processes
Pros and Cons
- "Because AWS Lambda is serverless, server configuration is not required, and we can run it directly anywhere."
- "If it is a specific ETL process or a long-term one, then AWS Lambda is not a good option."
What is our primary use case?
The primary use case is processing data. We use the pipeline multiple places to process the data. Whatever JSON files we get, we have to standardize, enrich, and also format to the application.
What is most valuable?
The most valuable feature is that it's serverless. Therefore, server configuration is not required, and we can run it directly anywhere. We can write Java code or Python code in that.
The initial setup is straightforward as well.
AWS Lambda is good for short-term automation processes.
What needs improvement?
If you want to run processing data, which takes less than 15 minutes, then you can use Lambda. However, if it is a specific ETL process or a long-term one, then AWS Lambda is not a good option.
The longer Lambda runs, the higher is the cost incurred because the cost is based on runtime.
At times, it hard to know when Lambda should be used and when it should not. So in the future, if there are serverless extensions, it would be fine.
For how long have I used the solution?
I've been working with AWS Lambda for six to seven months.
How was the initial setup?
The initial setup of AWS Lambda is straightforward.
What's my experience with pricing, setup cost, and licensing?
The cost of AWS Lambda is based on runtime.
What other advice do I have?
It's a good product, and we use Lambda for short run processes, for example, processing a file from the landing zone. Suppose FTP or SFTP has put a file in one landing area, and we have to push a file to the S3 bucket. We would not need to do any writing, shell scripting, or Linux coding, etc. In general, with Lambda you can get the Python coder or Java code.
So, professionals can easily perform these tasks within a short time. This will help with agile processes and sprints. My advice is that AWS Lambda is a good service for short-term automation processes.
I would rate AWS Lambda at eight on a scale from one to ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
AWS Lambda
December 2024
Learn what your peers think about AWS Lambda. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
IT Analyst at Tata Consultancy
Scales on demand, allowing us to focus on core business functions
Pros and Cons
- "The most valuable feature of this solution is the API Gateway."
- "The security needs to be improved."
What is our primary use case?
We use this solution for a mobile banking application with the ability to scale as per demand and to focus on core business functions rather than the platform.
How has it helped my organization?
This solution has improved our ability to scale as per demand and to focus on core business functions rather than the platform.
What is most valuable?
The most valuable feature of this solution is the API Gateway.
What needs improvement?
The security needs to be improved.
For how long have I used the solution?
I have been using this solution for one year.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Lead solution architect at a government with 1,001-5,000 employees
Scalable and responsive support
Pros and Cons
- "The support from AWS Lambda is very good, they are responsive."
- "AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job."
What is our primary use case?
AWS Lambda is used for the whole surface, it does the backups, and schedules, and learns some of the core functionalities but it can depend on the topic or application. The solution is used to build APIs and many other functions
What needs improvement?
AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job.
For how long have I used the solution?
I have been using AWS Lambda for approximately six years.
What do I think about the stability of the solution?
AWS Lambda is stable.
What do I think about the scalability of the solution?
AWS Lambda is in the cloud which makes it scalable.
I have worked in many companies that have used this solution and some of them had a lot of users.
How are customer service and support?
The support from AWS Lambda is very good, they are responsive.
What other advice do I have?
I rate AWS Lambda a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Member at a religious institution with self employed
Good integration with other AWS services, stable, and scalable
Pros and Cons
- "The programming language and the integration with other AWS services are the most valuable features."
- "Its performance can be improved. There should also be more dynamic security permissions."
What is our primary use case?
We use it for serverless functions.
What is most valuable?
The programming language and the integration with other AWS services are the most valuable features.
What needs improvement?
Its performance can be improved. There should also be more dynamic security permissions.
For how long have I used the solution?
I have been using this solution since I joined this company, which was two years ago.
What do I think about the stability of the solution?
It is very stable.
What do I think about the scalability of the solution?
It is very scalable.
How are customer service and support?
There are no issues. So far, I am completely satisfied with their technical support.
How was the initial setup?
It was easy.
What about the implementation team?
I did it myself.
Which other solutions did I evaluate?
We didn't evaluate other options because it was a requirement for the project.
What other advice do I have?
I would advise others to predefine the main model and ensure their CI/CD pipeline.
I am satisfied with Lambda, and I would recommend it to others. I would rate it an eight out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Architect - Database Administration at Mitra Innovation
Good monitoring and visibility but it's good if the timeout can be increased
Pros and Cons
- "The stability is good."
- "We've had to revamp the way that it works due to that 15-minute timeout limitation."
What is our primary use case?
We have used Lambda for
batch processing for specific schedules.
different bot functions that run regularly,
Application business logic
How has it helped my organization?
Easy to impliment without any environment provisioning
What is most valuable?
The initial setup is straightforward.
The stability is good.
It has good monitoring. the visibility is great.
What needs improvement?
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.
For how long have I used the solution?
We've been using over 2 years
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I've never dealt with technical support. I can't comment on their services.
How would you rate customer service and support?
Positive
How was the initial setup?
It seems to be a straightforward process. However, I'm not directly totally involved with the Lambda implementation.
What about the implementation team?
We are implementors and can set up the solution for clients.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
IT Analyst at Barakat Groip
It's good for companies of all sizes, and we've never had problems using it as a large enterprise
Pros and Cons
- "It's also suitable for companies of any size. For example, we're a large enterprise, and we've used Lambda without any problems in the last 10 months."
- "Lambda's dashboard could be more user-friendly and customizable. I want the dashboard to have more information to quickly identify what functions and events are running. Also, we want to be able to add more trigger points, push notifications, and events."
What is our primary use case?
Our website is hosted on AWS, and we use Lambda to create trigger points.
What needs improvement?
Lambda's dashboard could be more user-friendly and customizable. I want the dashboard to have more information to quickly identify what functions and events are running. Also, we want to be able to add more trigger points, push notifications, and events. For example, we have a shopping website, so we want to create some events to trigger batch notifications like SMS.
For how long have I used the solution?
I think my company implemented Lambda two years back, but I only joined 10 months ago.
What do I think about the stability of the solution?
Lambda is stable. We don't have any problems with this app.
What do I think about the scalability of the solution?
Many things are on running on the site, so there is no issue with scalability.
How are customer service and support?
We haven't had issues with this platform, so I haven't needed to contact support.
How was the initial setup?
Actually, I am not recommended that thing. Actually, it is sent by our vendors. Actually, they implemented that thing.
What other advice do I have?
I rate AWS Lambda 10 out of 10. I can recommend Lambda. It's a good fit for our use case. It's also suitable for companies of any size. For example, we're a large enterprise, and we've used Lambda without any problems in the last 10 months.
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Head of Implementation and Security at a financial services firm with 1-10 employees
Has good performance and tech support
Pros and Cons
- "The solution offers good performance."
- "I wish to see better execution time in the next release."
What is our primary use case?
We are using the latest version.
We use the solution for the building of small applications.
What is most valuable?
The solution offers good performance. It is a good tool for developers.
What needs improvement?
I wish to see better execution time in the next release.
For how long have I used the solution?
I believe we have been using AWS Lambda for around a year.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is sufficiently scalable.
We have plans to increase its usage.
How are customer service and support?
I am satisfied with Amazon tech support.
How was the initial setup?
The initial setup is fine.
Its duration varies with the application that one is deploying.
What about the implementation team?
The installation can be accomplished on one's own.
What's my experience with pricing, setup cost, and licensing?
The solution is pay as you go.
Which other solutions did I evaluate?
To the best of my knowledge, we have been using the solution from the get go.
What other advice do I have?
There are 100 end users making use of the solution in our organization.
I would recommend the solution to others.
The solution is recommended for those who have event-based applications.
I rate Lambda AWS as a nine-point-five out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free AWS Lambda Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Product Categories
Compute ServicePopular Comparisons
Apache Spark
AWS Batch
AWS Fargate
Apache NiFi
Amazon EC2 Auto Scaling
Amazon EC2
Oracle Compute Cloud Service
Apache Storm
Amazon Elastic Inference
Buyer's Guide
Download our free AWS Lambda Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Which is better, AWS Lambda or Batch?
- Which solution should I use for the creation of a serverless application: AWS Lambda or Azure?
- How would you recommend selecting a compute and storage solution based on the company size?
- When evaluating Compute Service, what aspect do you think is the most important to look for?
- What is quantum computing? How does it work?
- What is the best compute service solution?
- What should I look for in a compute service solution?
- What is serverless computing? What are the benefits of using this technology?
- Why is Compute Service important for companies?