AWS Lambda Reviews

For over a year, I worked in an IoT company, where we had some web applications. I used AWS Lambda in all of our devices for connection. During this time, I also taught AWS, using Lambda to help my students learn how the code of infrastructure works.

What I like most about AWS Lambda is that it's very easy to deploy. You basically have to click a couple of buttons, and suddenly you have a Lambda function that works. Obviously, then you have to write all the code, however, that it's a good service for beginners. 

Additionally, encapsulating code in Lambda functions makes applications easier to maintain and scale better than having one EC2 instance hosting everything. I think scalability and maintenance are major advantages. 

Also, the ability to work with different versions of Python is useful; sometimes I want to use different libraries unavailable in some versions.

The way Lambda works with HTTP headers is a bit odd. It needs some change as the configuration is somewhat hidden, so I don't really know what I'm changing. Managing the HTTP headers should be modified for clarity since, at least in my case, I found it challenging to configure and manage them initially. I would suggest that this is an area for improvement.

I have used Lambda for over a year.

I have never had issues with Lambda's stability. The first executions may have a bit of latency due to the cold start, however, once the Lambda is up, everything is much faster. It's a fast service, yet, in cases where the Lambda has been idle for a long time and has to restart, it's a bit slower. However, I think it's still something manageable.

I have found that Lambda has no problem with scalability. I can have many Lambdas working simultaneously. In case there is a traffic peak, AWS manages the scalability itself. I don't need to configure anything. It's all done by AWS, and for me, it has always worked perfectly. I have never seen any problem with that.

If I want a Lambda ready to go with no configurations, it's easy. I just click a few times, and it works. I don't need to know how it works underneath. However, if I want something more complex, for example, working with HTTP headers, it gets complex.

In the same way I used Lambda, I would say that no, I did not. It's a very unique service.

I would give it a nine out of ten.

The best thing to do is to pick a programming language you already know. Instead of starting with GitHub actions or workflows, it's better to make the Lambda public, start coding directly into the Lambda editor, and see how everything works. Try to understand how executions are logged into CloudTrail. 

When you gain more experience, obviously, Lambda should not be public, and you can make more complex things, like working with headers and authentication and connections to other AWS services.

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.

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.

Our primary use case for Lambda is for serverless computing in our project. We have an environment in AWS with Lambda, EC2, S3, SQS, RDS, and Redshift. Our Lambda function is triggered whenever a new object is put into S3. It will validate, extract data from S3 then input metadata into MySQL and put the main data into Redshift as the data warehouse. An SQS message will be created so our Application in EC2 is alerted that there is new data to have processed.

With AWS Lambda, we found it easy to integrate with other AWS services such as S3, SQS, RDS, etc. This allows us to scale our services in an almost unlimited fashion, as data input into S3 sometimes peak up to a thousand objects and need to be processed as soon as possible.

This solution is easy to integrate with other AWS services, making our job easier and more effective. Lambda is lightweight and we can quickly develop our functions. The ability to scale up and down very quickly helps because we can maintain our system performance and business at a low cost.

There are several things that can be improved, including:

• It has limited access to disk space, as it does not have full access to underline VM
• Lamba functions have cold-starts that can cause some delay
• It is hard to troubleshoot and monitor Lambda functions

Our Lambda functions are very stable, despite the fact that we have scaled up and down frequently. This means our functions run in the different underlying hosts, but their behavior is still the same.

This solution can scale up to thousands of instances in a very short time without any delay. It is very fast.

We have just started with Lambda and it is great.

Setting up AWS Lambda is simple and AWS provides great documentation that includes installation details, as well as guidelines and best practices. The coding of Lambda functions is simple and straightforward with our developer.

We implemented using our in-house team.

With Lambda, we can reduce the time to deliver our project to production and can provide our clients with a scalable, reliable, and high-performance system.

We considered deploying our functions in EC2 with Auto Scaling but decided on Lambda as we need a lightweight function that is able to scale up and down quickly. Also, the overall cost is much lower.

Implementing this solution is easy, with just a few clicks your function will be ready. I suggest reviewing your requirements and choosing a suitable Lamba function size. Also, have a good strategy on how to trigger your functions.

I use AWS Lambda for serverless services to avoid running applications on an instance. I use it for my personal website. When people want to view my website, the service is trigger-based, so it only operates when accessed, allowing for cost efficiency.

I like AWS Lambda as it is cheaper compared to other AWS services that require applications to be running continuously. Lambda is trigger-based, which means it only activates when accessed, ensuring cost savings. 

It's also serverless and makes processes easier despite the initial difficulty in setting it up. Being able to configure Lambda to work in a trigger-based manner is highly beneficial for my needs.

AWS Lambda is a bit difficult to set up if someone doesn't know how to code. It would be helpful to have a chatbot or resource that can guide users through the process, especially for those not proficient in coding. Setting up workflows that connect multiple AWS services can be challenging without guided support.

I've been using AWS Lambda for some months now.

There are no stability issues. AWS Lambda is very fast and secure, and I've not encountered any problems with it.

AWS Lambda's scalability depends on the number of users. It might not handle a high volume of requests efficiently, so it's better suited for small-scale operations where the number of users is limited.

The initial setup of AWS Lambda can be difficult, especially for those who do not know how to code. It took me about a week to set it up properly.

I am the only person maintaining the AWS Lambda setup.

I can't provide specific cost savings numbers, yet, due to the fact that AWS Lambda is trigger-based, it offers cost savings compared to instances that are always running.

AWS Lambda is cheaper compared to running an instance continuously. You only pay for what you use, making it cost-effective.

I would recommend AWS Lambda based on the use case. It's suitable for small applications where user access is limited. However, it's not ideal for large-scale platforms due to limitations in managing high traffic. 

I rate AWS Lambda a seven out of ten.

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.

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.

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.