My primary use cases for AWS Lambda is collecting data from other systems through API, pre-calculations, and ETL.
Head of Algorithms at Stealth Startup
Serverless solution with many use cases
Pros and Cons
- "The feature I found most valuable about Lambda is the fact that it's serverless."
- "I would like the layers to have a bigger volume. I would like to be able to add more. I don't want to be limited by the layer."
What is our primary use case?
What is most valuable?
The feature I found most valuable about Lambda is the fact that it's serverless.
What needs improvement?
I would like the layers to have a bigger volume. I would like to be able to add more. I don't want to be limited by the layer.
In addition, writing temporary data to Lambda is not straightforward. Sometimes I use the S3 for that. I found it a little bit challenging.
For how long have I used the solution?
I have been using AWS Lambda for a couple of years.
Buyer's Guide
AWS Lambda
November 2024
Learn what your peers think about AWS Lambda. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,649 professionals have used our research since 2012.
What do I think about the stability of the solution?
My impression is that it is a stable solution.
What do I think about the scalability of the solution?
I would rate the scalability of this solution a 10, on a scale of one to 10, with one being not scalable and 10 being very scalable.
How are customer service and support?
I have never used Amazon's tech support.
How was the initial setup?
I would say the initial setup was straightforward.
We required two technical staff to do the deployment and maintenance.
We have about 15 to 20 users of Lambda in our company and plan to expand.
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.
CEO - Founder / Principal Data Scientist / Principal AI Architect at Kanayma LLC
Serverless compute server used for data processing type transformations from one source to a target
Pros and Cons
- "Lambda has improved our organization by making it possible to transform data."
- "Lambda has limitations on the amount of memory you can use and is not a good solution for long running processes."
What is our primary use case?
There a variety of use cases for this solution but it is mostly used for data processing type transformations from one source to a target. In instances when Lambda works well, we are planning to increase usage.
Deployment and maintenance of Lambda requires two people but this may increase depending on the size of the deployment.
How has it helped my organization?
Lambda has improved our organization by making it possible to transform data.
What needs improvement?
Lambda has limitations on the amount of memory you can use and is not a good solution for long running processes. If the amount of data is reasonably small, it will run and transform successfully. If you have tons of data coming in, it stops working and you have to restart it.
The orchestration and coordination between different Lambdas could also be improved.
For how long have I used the solution?
I have used this solution or a couple of years.
What do I think about the stability of the solution?
This is a fairly stable solution.
What do I think about the scalability of the solution?
This solution has some limitations on scalability due to the problem with coordination between the different Lambdas. Is it not very straightforward and you have to do a lot of testing.
How was the initial setup?
The initial setup was fairly straightforward.
What other advice do I have?
I would advise others to use it in those circumstances where it works well and to be aware of the problems with coordination and orchestration. Make sure that it doesn't have to process tons of data.
I would rate this solution a seven 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.
Buyer's Guide
AWS Lambda
November 2024
Learn what your peers think about AWS Lambda. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,649 professionals have used our research since 2012.
Cloud DevOps engineer at DeepMetis
An inexpensive tool that's feature-rich, stable, and supports different languages
Pros and Cons
- "What I like best about AWS Lambda is that it's feature-rich, and I appreciate that. I also like that it's stable and supports many languages."
- "What could be improved in AWS Lambda is a tricky question because I base the area for improvement on a specific matrix, for example, latency, so I'm still determining if I can be the judge on that. However, room for improvement could be when you're using AWS Lambda as a backend, it can be challenging to use it for monitoring. Monitoring is critical in development, and I don't have much expertise in the area, but you can use other services such as Xray. I found that monitoring on AWS Lambda is a challenge. The tool needs better monitoring. Another area for improvement in AWS Lambda is the cold start, where it takes some time to invoke a function the first time, but after that, invoking it becomes swift. Still, there's room for improvement in that AWS Lambda process. In the next release of AWS Lambda, I'd like AWS to improve monitoring so that I can monitor codes better."
What is our primary use case?
AWS Lambda is mainly used for automation. To simplify, in AWS Lambda, I define a function, and I can invoke that function or feature whenever I want and on schedule.
For example, if I have data to collect daily from different services, I schedule the AWS Lambda function to do that, and it does the job. That's one of the use cases of the tool.
Another use case for AWS Lambda is when you have multiple servers running and need to shut down the servers at night. You can configure an AWS Lambda function that would shut down the servers every night on schedule. You can also use it as a backend and invoke it through API, so you deploy your backend from an AWS Lambda function, then link it with the API gateway, then you can invoke your function through the API.
What is most valuable?
What I like best about AWS Lambda is that it's feature-rich, and I appreciate that. I also like that it's stable and supports many languages.
What needs improvement?
What could be improved in AWS Lambda is a tricky question because I base the area for improvement on a specific matrix, for example, latency, so I'm still determining if I can be the judge on that. However, room for improvement could be when you're using AWS Lambda as a backend, it can be challenging to use it for monitoring. Monitoring is critical in development, and I don't have much expertise in the area, but you can use other services such as Xray. I found that monitoring on AWS Lambda is a challenge. The tool needs better monitoring.
Another area for improvement in AWS Lambda is the cold start, where it takes some time to invoke a function the first time, but after that, invoking it becomes swift. Still, there's room for improvement in that AWS Lambda process.
In the next release of AWS Lambda, I'd like AWS to improve monitoring so that I can monitor codes better.
For how long have I used the solution?
I've been using AWS Lambda for one year and a half.
What do I think about the stability of the solution?
AWS Lambda is a stable product.
How are customer service and support?
I have yet to contact the AWS Lambda technical support team because I haven't experienced any difficulty with the tool.
Which solution did I use previously and why did I switch?
One of the reasons my company went with AWS Lambda is that it's serverless, so you don't need to manage any server because AWS will handle it. This means that a lot of responsibilities will be taken care of by AWS, which helps you avoid many problems.
Another reason for choosing AWS Lambda is its stability. Latency is also not a problem on AWS Lambda, allowing you to use different services in your AWS account securely. For example, when you want to reach the AWS billing service, you can do it within the environment of your AWS account without an external tool, which makes it very secure. AWS Lambda also helps you reach other AWS accounts securely because it depends on roles rather than search keys or passwords.
How was the initial setup?
The initial setup for AWS Lambda is straightforward. It's effortless to start using AWS Lambda.
What's my experience with pricing, setup cost, and licensing?
Price-wise, AWS Lambda is very cheap. It's not free, but it's not that expensive.
What other advice do I have?
I'm using the latest version of AWS Lambda because when a framework or tool is deployed on a public cloud, it's always the newest version, and you don't get to choose the version.
I'd tell first-time users of AWS Lambda, or anyone looking into using the tool, that you can deploy every application within AWS Lambda, and it's very easy to set up and deploy. You can also use it with any application regardless of language because AWS Lambda supports many languages such as Go, Bison, Node, GS, and .NET. The tool is very code-agnostic, and not coded with programming languages, so you can still use Docker images to start your AWS Lambda function, for example.
My rating for AWS Lambda is nine out of ten because of how hard AWS worked on having good latency, security, and an intuitive start. The tool supports different languages and is stable, so I gave it a high rating.
I'm a customer of AWS Lambda.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Specialist at RateGain
Should improve its compatibility with the language used to write the code, though it can be used for testing applications
Pros and Cons
- "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."
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using AWS Lambda for six months.
What do I think about the scalability of the solution?
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.
How are customer service and support?
I faced some challenges when we worked on the migration. I raised tickets to the support team, and they helped me.
How was the initial setup?
The solution's initial setup can be done with the help of documents.
What's my experience with pricing, setup cost, and licensing?
AWS Lambda is not expensive for micro testing but is expensive if used for long deployment or long services.
What other advice do I have?
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.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jul 18, 2024
Flag as inappropriateDevOps Engineer at United Vision
A great solution for automation and tagging and has helped our organization with cost optimization
Pros and Cons
- "The automation feature is valuable."
- "The runtime for the solution can be improved."
What is our primary use case?
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.
How has it helped my organization?
The solution has helped our organization with cost optimization. So we have used AWS Lambda for consolidated billing.
What is most valuable?
The automation feature is valuable.
What needs improvement?
The runtime for the solution can be improved.
For how long have I used the solution?
We have been using the solution for approximately two years.
What do I think about the stability of the solution?
The solution is stable. I rate it a nine out of ten.
What do I think about the scalability of the solution?
The solution is scalable, and I rate it a ten out of ten.
How was the initial setup?
The initial setup was straightforward.
What's my experience with pricing, setup cost, and licensing?
The solution is very expensive.
What other advice do I have?
I rate the solution a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Genesys Cloud Consultant / Software Engineer at Hightelecom
There is no server implementation and no maintenance, but there are server consumption limitations
Pros and Cons
- "The most valuable feature is that there is no need to implement it in a server because it is a service."
- "The 60 seconds limitation with the consumption of the service is really restrictive for a service and the solution can be improved by eliminating that."
What is our primary use case?
We have some services deployed that we need to consume in Lambda because it's a faster and better implementation. We have a model that microservice in the product, which we implement in AWS. For that reason, we use Lambda.
How has it helped my organization?
The solution has improved our organization by providing us with better communication with the different services, dependencies, and implementations our clients require. The solution is faster and the consumption is really good.
There are some restrictions. For example, we have some services that if you have more than 60 seconds in consumption of this service, we don't use it, because they have that restriction with the gateway. Those services we implement with Fargate and with Docker.
What is most valuable?
The most valuable feature is that there is no need to implement it in a server because it is a service.
What needs improvement?
The 60 seconds limitation with the consumption of the service is really restrictive for a service and the solution can be improved by eliminating that.
For how long have I used the solution?
I have been using the solution for one 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 scalable.
How was the initial setup?
The initial setup is easy but you do need some experience.
What about the implementation team?
The implementation was completed in-house.
What was our ROI?
The return on investment is good because it is a Cloud-based solution that doesn't require maintenance or a server on-premises saving you money.
What other advice do I have?
I give the solution a seven out of ten.
One person with AWS knowledge is sufficient for deploying and maintaining the solution.
We currently have around 160 people using the solution.
All of the products we implement are in AWS so we do have plans to increase the usage of Lambda, Fargate, and all of the services in AWS to help speed up the implementations.
For anyone thinking about using the solution, you must make sure you have some experience in AWS or another cloud, maybe Azure, and have some experience with software development. If you don't have software development skills, maybe you have experience in deploying services on IIS or something like that.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Director Of Sales Marketing at a energy/utilities company with 10,001+ employees
Has good real-time performance
Pros and Cons
- "One of the most valuable features of AWS Lambda is the performance. Lambda is very technical and has very high performance, as well as good real-time performance."
- "AWS Lambda could be improved with better stability."
What is our primary use case?
We are primarily using AWS Lambda for real-time API services. We use AWS Redshift to support our Lambda code functions.
This solution is cloud-based.
What is most valuable?
One of the most valuable features of AWS Lambda is the performance. Lambda is very technical and has very high performance, as well as good real-time performance.
What needs improvement?
AWS Lambda could be improved with better stability.
For how long have I used the solution?
I have been using AWS Lambda for more than two years.
What do I think about the stability of the solution?
This solution is very, very stable.
What do I think about the scalability of the solution?
In our organization, there are around 300 users of AWS Lambda. We have plans to increase our usage.
How are customer service and support?
I have contacted Amazon's technical support, and they were very excellent.
How was the initial setup?
The installation is straightforward. The process took us under three hours, and we did it ourselves. For deployment and maintenance, we have a team of 10 engineers and developers.
What about the implementation team?
We implemented this solution through an in-house team.
What's my experience with pricing, setup cost, and licensing?
For licensing, we pay a yearly subscription.
What other advice do I have?
I rate AWS Lambda a nine out of ten. To those looking to implement AWS Lambda, I would recommend this solution, and say that Lambda has a learning curve in order to enhance the service when using it for the first time. I would advise the user to study hard to use Lambda as a tool.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CEO at a healthcare company with 51-200 employees
It does all the management and has great scalability and stability
Pros and Cons
- "The cool thing about AWS Lambda is that AWS does all the management. For compression, it is all about making the data small and then making it regular size again. We have an encode function and a decode function. AWS Lambda schedules each of those for us. It has a load balancer and all the fancy stuff, depending on the demand. The most valuable part of AWS Lambda is that I only need to write the software. I need to write two functions, and my cloud developer turns them into two AWS Lambda instances. That's it."
- "One area of improvement is to include support for more programming languages. AWS Lambda does not support a lot of programming languages. You have to write the Lambda functions in a certain programming language. We are using C++. My developer knows a couple of other languages. Python is his favorite language, but Python is not supported in AWS Lambda."
What is our primary use case?
We are a startup, and we are doing faster and cheaper storage for IT. We are going to offer our storage services in about two months, and we are starting with AWS. We do lossless compression using microservices. We do the compute in a lossless compression way similar to gzip, WinZip, or PKZIP, except that we are giving a discount to customers.
The product that we are developing is not yet in the market. We are doing alpha testing for select customers who are using AWS. The biggest advantage is that you get faster storage without doing a forklift upgrade, and you get 35% cheaper storage. So, you get 2X faster storage with a 35% to 50% lower monthly bill.
We use AWS Lambda to encode and decode data. I work on the encode and decode software. I am working with a cloud developer. He works on the Lambda deliverable and wraps my C code with his C++ wrappers. They get bundled together with no JS stuff.
What is most valuable?
The cool thing about AWS Lambda is that AWS does all the management. For compression, it is all about making the data small and then making it regular size again. We have an encode function and a decode function. AWS Lambda schedules each of those for us. It has a load balancer and all the fancy stuff, depending on the demand.
The most valuable part of AWS Lambda is that I only need to write the software. I need to write two functions, and my cloud developer turns them into two AWS Lambda instances. That's it.
What needs improvement?
One area of improvement is to include support for more programming languages. AWS Lambda does not support a lot of programming languages. You have to write the Lambda functions in a certain programming language. We are using C++. My developer knows a couple of other languages. Python is his favorite language, but Python is not supported in AWS Lambda.
For how long have I used the solution?
I have been using AWS Lambda since it came out in 2016.
What do I think about the stability of the solution?
It is very stable.
What do I think about the scalability of the solution?
Its scalability is great. We write an encode function, and my cloud developer turns that into an AWS Lambda instance. We then write a decode function, and he turns it into another AWS Lambda instance. We just hook it up and use an API gateway for doing the security check, encryption, and other things.
How are customer service and technical support?
We did not require any support. Most of the stuff in the cloud is anyways self-serve.
How was the initial setup?
The initial setup was straightforward.
What other advice do I have?
They have a program for AWS customers called Activate. With the Activate program, you can get compute and storage credits. They gave us like $10,000 worth of credit over 18 months.
I would recommend using this solution. It was the first microservice. It doesn't have much overhead, and it does what it claims to do.
I would rate AWS Lambda an eight out of ten. It is a good solution.
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.
Buyer's Guide
Download our free AWS Lambda Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Compute ServicePopular Comparisons
Azure Stream Analytics
Apache Spark
Google Cloud Dataflow
AWS Batch
AWS Fargate
Apache NiFi
Amazon EC2 Auto Scaling
Amazon EC2
Oracle Compute Cloud Service
Apache Storm
Amazon Elastic Inference
StackStorm
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?