AWS Lambda Reviews

We are using the latest version.

We use the solution for the building of small applications.

The solution offers good performance. It is a good tool for developers. 

I wish to see better execution time in the next release. 

I believe we have been using AWS Lambda for around a year.

The solution is stable. 

The solution is sufficiently scalable. 

We have plans to increase its usage. 

I am satisfied with Amazon tech support. 

The initial setup is fine. 

Its duration varies with the application that one is deploying. 

The installation can be accomplished on one's own. 

The solution is pay as you go.

To the best of my knowledge, we have been using the solution from the get go. 

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. 

In respect of the function and template, I find the solution to be easy to use, as it obviates the need to do the same thing repeatedly. 

The automation with other Amazon products could be better. 

As the solution is on-cloud, it is already scalable. 

There is another local team with whom we work when it comes to the need for technical support. 

The installation and configuration of the solution is straightforward. 

The length of the deployment can vary with the solution. It took us half a day but, when accounting for the configurations and connectivity, all told, this can take about one or two days. 

The cloud team consists of 47 people. 

The solution is deployed on-cloud. 

In the past year, we have around 75 to 80 Lambda functions. 

The solution provides basic security standards.

I would recommend the solution to others. 

I rate AWS Lambda as a five to six out of ten. 

We use AWS Lambda to automatically manages some compute resources.

It triggers and screens some of my services.

It is easy to use.

I like the way it manages.

I would like to see more integration with other platforms.

I have been using AWS Lambda for a few years.

We are not using the latest version.

AWS Lambda is a stable solution.

You do not have to scale AWS Lambda, it automatically scales for you.

AWS Lambda is used on a daily basis.

We only have a few people who used this solution. I have two teams.

We have a dedicated manager.

My experience with support so far has been good.

It doesn't require any installation at all.

AWS Lambda is inexpensive.

I am very happy with this solution. I would recommend it to others who are interested in it.

I would rate AWS Lambda an eight out of ten.

The product is primarily used to deploy code and provision a software solution to your clients when they don't have the time. You don't have to pay for the servers and the uptime.

It is my preferred product, as it provides me with source code within the solution.

It's a great product due to the fact that you don't have to pay for the servers and the uptime.

The solution is very stable.

The product scales well. 

The solution can be free to use.

The product could make the process of integration easier. 

The could be more integration testing. The internal is great with Lambda, however, I have to make sure I have done my tests on a related machine before deploying.

I've been using the solution for three years. I haven't used it for too long just yet.

The solution is very stable. There are no bugs or glitches. It does not crash or freeze. It's reliable.

The solution scales very well. If a company needs to expand it, it can do so.

Its scalability is always based on how much software there is. It's actually virtually building out. The API can scale up automatically. And if the API calls go down, then the system slows in real-time.

All my clients are using the product. All the projects I push to my clients are on Lambda.

I haven't dealt with technical support directly. Therefore, I can't speak to how helpful or responsive they are in general. I don't have experience with them on that personal level. 

There is no setup process to deal with as the entire solution is on the cloud. It's very easy.

If you need to deploy it to a license, the first server you use you need to pay for a license. If you're going to open-source, there are no licenses required.

I'm just a customer and have clients on the solution.

I've had a very good experience with the product. I would rate it at a ten out of ten.

I would recommend the product to all developers.

We have some APIs and we use some mechanisms to process these APIs. Normally, some APIs need to be hosted by some servers. However, with this product, we can compute everything serverless.

The solution is designed very well. You don't need to keep a server up. You just need some router to route your API request and Lambda provides a very well-designed feature to process the request. 

From our perspective, the solution works for a variety of scenarios.

It's very straightforward and very easy to use. We don't need to keep several apps. We just use some APIs and to route with the APIs to create related Lambda functions.

The kind of scenarios we can leverage in Lambda can be difficult. For example, we have a lot of their servers that provide APIs. Before, the APIs were hosted by a server. We have identified that some of them can be hosted in Lambda. That's a challenge as we're yet to think of our scenario and match our requirements in order to really leverage Lambda. That's more on us than the solution itself.

We need to better understand Lambda for different scenarios. We need some joint effort between Amazon and the users to have the users identify how they can really leverage Lambda. It's not about Lambda itself; it's about the practice, the guidance. There needs to be very good documentation. From the user perspective, what exists now is not always enough.

Lambda is stable. We don't see any problems so far. There haven't been bugs or glitches and it doesn't crash or freeze on us.

The solution is very scalable. We just allocated a very small number of requirements to Lambda. We've still found it to be very scalable.

We are a technology company, so we do not have many users. Most are developers, engineers, and architects.

So far, we've found the technical support to be okay. They are knowledgeable and responsive and we are satisfied with the level of support we get.

The initial setup's level of difficulty depends on different requirements. Normally, we can see that number to process and do a straight comparative analysis for a simple scenario. The deployment is fine for the most part. We don't spend much time on it in comparison to a traditional deployment. It's very quick.

When you try some services, with Amazon, the first phase is okay. When we continued with more workloads placed on Amazon, we needed to take into account the cost, as the cost to the firm becomes more and more. It can get expensive if you aren't careful.

We're just a customer. We don't have a business relationship with the company.

Lambda is very good. I don't collect feedback from other colleagues or other members. However, from my perspective, Lambda is good. I would rate it nine out of ten, based on my experience alone.

The best advice I can give other organizations is that it's better to consider your scenarios and see what is scenario is suitable for the functions or services you require, or not. Don't try to move your applications just because of new technology and new concepts. Consider carefully your requirements and that will help you avoid some additional costs.

Our primary use case is for our financial institutions. We use it for many customers that we work with. We develop solutions for our customers and run them on AWS. We wanted to build the solution on the public cloud and out of all the public cloud providers, AWS is the best. It has a rich set of services. 

It's a serverless solution which is the best feature. It helps us because it offers free aspects. From the infrastructure perspective, it helps us manage costs. There is no overhead of estimating how much infrastructure we're going to need. We can focus on building the business functionality that we want to build. 

Lambda didn't use to support all the capabilities, if you wanted to initialize it before started serving the requests, it is not possible. In the most recent upgrades, they have added this feature. There is nothing missing. If there is something missing, AWS has other solutions that covers it. I look at Lambda as a piece of AWS, working in conjunction with other solutions.  

I have been using AWS for two and a half years. 

We don't have any issues with stability or scalability. We have offline and online users. There are thousands of online users. 

Their support is excellent. We have no complaints. It can be expensive, we bought the enterprise support. If you don't want to spend the money, you might run into issues but that isn't the case for us. 

Everything was set up in the public cloud. We didn't need to set up a lot of things. We didn't have to connect a lot of connectivities to external applications. If you are setting it up on hybrid solution, there is a lot of work that needs to go in. You need to understand what your organization's security standards are, how the different teams are going to access the infrastructure, etc. For hybrid, it will take a lot of time but for only the public cloud, it is quite easy. 

AWS is slightly more expensive than Azure. But from a maturity perspective, AWS is way more ahead than Azure. 

I would rate it a nine out of ten. It was missing features like initialization but they are available now in the latest release. 

It is good for smaller companies that don't have a lot of staff that will manage the infrastructure. It automatically scales based on the users and allocating the resources. From a cost perspective, it is quite cheap. It takes out a lot of overhead. If it's for a large company with a lot of experts, there are other good solutions. 

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 have only used it for a few services. It's still in POC mode. We haven't done any production on it currently. 

The most valuable feature is that it scans the cloud system and if they are any security anomalies it triggers an email. 

The running time of AWS Lambda runs fine. It takes around five minutes but it would be great if that time could be extended. 

I have been using Lambda for two to three years. 

We haven't seen any issues regarding stability as of now.

It is easy to expand the platform.

Their technical support is quite good. We have enterprise support, so it is quite good.

The initial setup is easy. 

I did the deployment with the help of consultants. 

I would recommend Lambda to someone considering it. 

I would rate it an eight out of ten. 

The pricing is similar to Azure services, they are quite competitive pricing-wise if you compare Azure and AWS.