AWS Lambda Reviews

Primarily, I work with all my clients to provide them with solutions. We are a service company, so we work with clients to define and build applications that resolve their need for automation issues. I create the solutions, and then there is a delivery team of mine which works to deliver that solution to the client.  

The thing that I have found most valuable in Lambda is primarily the ease of developing the services we distribute. We can easily develop the solutions using any language which is available today — this includes all the primary and new-age languages.  

Secondly, because it is a cloud service technology, we do not have to worry about the infrastructure behind the solutions we provide. Everything is all on the cloud and there is no maintenance and we have to do no monitoring of the architecture. The time and expense of maintenance are taken care of by the platform itself. Those are the things that we like most about it.  

There are certain limitations to some services in Lambda which will have to be overcome over time. Primarily, I think there are two aspects of the product that are in most need of improvement.  

One is, of course, the customization. The process of customizing should be simplified.  

The other is specifically in the area of integration. The configuration requirements for the services which would be desirable to integrate with Lambda are not always as easy to utilize as they should be. For example, the opportunities we have to integrate solutions with the world outside of the cloud are not well supported. These integrations are supported well inside the cloud but some clients need to support solutions outside the cloud. If somebody has that need we should be able to deploy integrations with products and services outside the cloud as well. 

So those are the two drawbacks and potential areas for improvement area which I would like to see corrected in AWS. Those features need to be updated because the current functionality of the product is not competitive enough today with other products in the category. I think with time they have to improve and add new features or offer other ways of integrating new services.  

I have been working for more than a year now on Lambda AWS (Amazon Web Services) solutions, designing the real-time applications, services, and similar types of solutions for automated response.  

Stability-wise, Lambda needs some improvement because it has constraints that cause issues with task completion. What I mean by constraints is that there are some limitations to the number of minutes that a process can run and then execute. If the process continues to run and goes beyond that limit, it will time out. Those kinds of things are built into the nature of the product. Probably with time I think this is an area where the company will need to add new features or functionality to improve the behavior.  

Lambda definitely is scalable and to a great extent because it does not require any kind of additional infrastructure for the clients. It just is just a lot less trouble to deploy. You can extend and auto-scale to any level. So, the scalability is very good.  

Our clients are large-sized enterprise businesses so certainly the product can scale up to meet their needs.  

The support from AWS is fine. I am quite definitely satisfied with their support system.  

I would say the setup is straightforward. I think that most of the development is really straightforward in nature. The solutions have to develop based on some use-cases defined by the client organization. When these are defined, we are just meeting the needs of the organization by building the solution to do what they need. So the setup and implementation are all pretty straightforward.  

I would definitely recommend AWS Lambda. There are a lot of successful test cases both with our clients and other startups which are doing really well using Lambda as a solution.  

On a scale from one to ten where one is the worst and ten is the best, I would rate AWS Lambda as an eight-out-of-ten. That would be the right number at this time considering the product is lacking in some areas.  

We had to deploy some serverless Node.js applications.

The solution works for small applications. It is a serverless tool that is quick to spin up. We needn’t consider anything in the bag.

I want to see support for longer applications. I need the 15-minute time-out window to improve.

I have been using the solution for about two to three years.

The tool is stable and you can rely on it for production service.

I think there were no issues with the size of the application we used, so I didn't see any noticeable scaling issues with Lambda. It's overall a good service.

The tech support is always good but it depends on the type of plan. We use the enterprise support plan which offers quick responses.

Positive

The initial setup was straightforward.

I would rate the tool’s pricing a nine out of ten. The solution’s pricing works on a pay-as-you-go basis.

I would rate the solution a nine out of ten.

We're using AWS Lambda to trigger jobs and receive SQS messages. We're also using the tool as a single unit where you have computing, storage, and network.

AWS Lambda has improved my company through its usage in a distributed system, particularly event-driven architecture. When an event is passed to AWS Lambda from Amazon SQS asynchronously, the tool can call an ETL job, and it can trigger that job, and that job can trigger an AWS Lambda function, which can then send a message to the queue to complete the entire use case.

The most valuable feature of AWS Lambda is that you can trigger and run jobs instantly, and after you complete the job, that function is either destroyed or stopped.

The feature to attach external storage, such as an S3 or elastic storage, must be added to AWS Lambda. This is its area for improvement.

I've been using AWS Lambda for two years.

Stability-wise, AWS Lambda is an eight out of ten.

Scalability-wise, AWS Lambda is an eight out of ten.

I have not encountered any problems with AWS Lambda, so I didn't need to contact its technical support team.

We didn't use a different solution apart from AWS Lambda.

The initial setup for AWS Lambda was straightforward.

I saw ROI from AWS Lambda.

Price-wise, AWS Lambda is a five out of ten.

One person is enough for maintenance for a cloud-based tool, such as AWS Lambda.

I cannot share the number of AWS Lambda direct users in my company, as that figure is confidential.

My advice to others looking into implementing the tool is that it's easy to use as long as you know the basics.

AWS Lambda has good features, so I'm giving it an eight out of ten.

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.

The solution has helped our organization with cost optimization. So we have used AWS Lambda for consolidated billing.

The automation feature is valuable.

The runtime for the solution can be improved.

We have been using the solution for approximately two years.

The solution is stable. I rate it a nine out of ten.

The solution is scalable, and I rate it a ten out of ten.

The initial setup was straightforward.

The solution is very expensive.

I rate the solution a nine out of ten.

The product serves as a function as a service, a serverless environment, you can say. It's a serverless environment, or, as some people call it, function as a service, FaaS.

We have been using it as a mobile backend. We have a mobile frontend, a mobile application, which uses the AWS Lambda functions running in the cloud. It serves as an API backend for a mobile application that is running in the frontend.

The solution is highly scalable.

The solution has proven itself to be stable.

The initial setup is straightforward. 

We've found the cost to be very good. It would be a great option for startups due to the low pricing.

The solution is very mature.

The user-friendliness of the solution could be improved. If it was easy to run with the same function in other platforms, other environments, that would make it more portable. That would be really good. User-friendliness and portability will be the two factors that need the most improvement.

The startup time sometimes needs to be faster, so that is one area of improvement. The startup time of each function can be slow. When it works the first time, it takes a little bit of time, so there's a minor delay. That could be improved.

The support of additional languages would improve the solution.

I've been using the solution for a couple of years at this point. It's been a while.

The solution is pretty mature by now. It's been there for a few years with AWS and they're continuously improving it. It's pretty mature. The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

The solution is highly scalable and also very cost-efficient. You only pay for the time, the duration of time and that's in maybe seconds, microseconds. You pay very little until you have very large-scale users. It is ideal for startups who want to deploy applications on the cloud.

While internally only our developers really use the solution, the mobile application is used by thousands of users globally.

We do plan to increase usage and will be adding more functions to our application.

While something was used before, it likely wasn't serverless. 

I'm aware that Oracle and Azure have certain options available.

The initial setup is not overly complex or difficult. It's very straightforward. 

The deployment times vary. It really depends on what you need to deploy.

Our developers managed the implementation process. A consultant or outside integrator was not required. It was all handled in-house.

The solution is very cost-efficient.

We are using the latest version of the solution currently. I cannot say which version number it is. I don't know it off-hand.

I'd rate the solution at an eight out of ten. We've been pretty happy with the capabilities so far.

I would recommend the solution to other organizations. This is much better than the other serverless solutions.

AWS Lambda needs to improve its stability. 

I have been using the solution for a couple of months. 

I would rate AWS Lambda an eight out of ten. 

The solution is scalable. I would rate it around eight out of ten. 

AWS Lambda is cheap. 

I would rate the tool an eight out of ten. 

AWS Lambda's best features are log analysis and event triggering and actioning.

AWS Lambda's GUI could be improved with a twist or tweak in its look and feel to make it more impressive.

AWS Lambda is reliable.

AWS's technical support is amazing - they can turn a case around in a single email.

The initial setup is straightforward as Lambda is a built-in feature of AWS services.

AWS Lambda is phenomenal with data, and I would rate it nine out of ten.

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.

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.

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.

I've been working with AWS Lambda for six to seven months.

The initial setup of AWS Lambda is straightforward.

The cost of AWS Lambda is based on runtime.

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.