AWS Lambda Reviews

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.

We have a DNS as a service and NAS as a service, which integrates, and we use Lambda functions there. We have a lot of applications that we use Lambda for. 

This solution is cloud-based. 

Some of the most valuable features are that it's easy to install and use. The performance is also good. 

Lambda could be improved in the sense that some of the things done with Lambda function take some time. So the performance could be better and faster. 

I have been using Lambda for many years. 

This solution is stable. 

This solution is scalable. 

I think, eventually, we will increase our usage. We need to move some of our services to Lambda. 

Amazon's technical support is good. 

Before implementing Lambda, we had legacy types of solutions. 

The installation could be faster, but I believe it's a straightforward process. I manage a team that handles the installation, so I can't comment on the specifics of the installation process. Within the team that handles maintenance and deployment, we have two engineers. 

We implemented this solution through an in-house team. 

We don't need to pay for licensing to use Lambda. 

I rate AWS Lambda an eight out of ten. I would recommend AWS Lambda to others. We provide a lot of services, part of which is that we write Lambda functions. 

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. 

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. 

I have been using AWS Lambda for more than two years. 

This solution is very, very stable. 

In our organization, there are around 300 users of AWS Lambda. We have plans to increase our usage. 

I have contacted Amazon's technical support, and they were very excellent. 

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. 

We implemented this solution through an in-house team. 

For licensing, we pay a yearly subscription. 

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.

My primary use case for this solution is usually for event-driven architecture. Since it's AWS, it's cloud-based. 

I have found all of the features valuable. It's an easy and cheap solution. 

AWS Lambda could be improved by increasing the size of the payload. Also, sometimes Lambda doesn't implement well for bigger solutions. 

I have been using this solution for three years. 

This solution is stable. 

I would rate customer support a nine out of ten. I have made three or four service requests and those were all resolved within 24 hours. 

I didn't use a different solution before implementing Lambda. 

The installation is straightforward. There isn't really anything you need to do. If you know exactly what you want, it can be done in five minutes. 

I implemented this solution myself. 

I pay for a monthly license. The licensing options will depend on the users. There's a monthly option and a yearly option. 

Lambda is a good and cheap solution and I would recommend it to those without a huge payload. There are around twenty or thirty people using Lambda in my organization. 

I would rate this solution an eight out of ten. 

We primarily use the solution for our backup coding for one of the ABDI services. We had a big job for the callout function, therefore we implemented Lambda here.

Lambda is the function we need to deploy any code.

We like that we don't require any infrastructure for it, which allows us a lot of cost savings.  

The solution has the capability to scale.

The product is quite stable.

The initial setup is pretty straightforward.

We've found the technical support to be very helpful.

It's a fairly easy solution to learn.

I can't recall any features that might be lacking. For us, it works quite well, however, it depends on what a company needs.

We'd love to see more integration potential in the future.

I've been using the solution for about two years at this point.

The solution has proven to be very reliable and quite stable. The performance is good. There are no bugs or glitches and it doesn't crash or freeze on us. 

The product scales well. If a company needs to expand, it should be possible to do so.

We have more than 5,000 users on the solution currently.

Technical support from Amazon is excellent. They are extremely helpful and we find they respond quickly. We're very happy with the level of support we receive. 

The initial setup is pretty straightforward. It's not overly difficult by any means. Ashish:
The Lambda function is not that hard to set up due to the fact that we generally go to the AWS services URL and we can easily find the Lambda function from there.

The solution really doesn't require that much maintenance. You don't need a big team on it at all.

The solution is fairly reasonable, and, as it doesn't require any infrastructure, can save a company a lot of money simply by being on the cloud.

We bought a license from AWS that renews yearly.

We're using the latest version of the solution. It automatically updates as it is based on the cloud.

I'd rate the solution at a nine out of ten. We are quite happy with its overall capabilities.

I'd recommend the solution to other users and other organizations. It's very easy to learn.

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.

AWS Lambda has serverless programming, like Logic Apps from Azure. You just configure the run-time and then they start coding. It is event-driven. It started with my obtaining Salesforce. Salesforce is a low-code and non-code program and totally SAS. Everything starts from the event, from the trigger. You get the trigger and you work at the program. You have some other models, maybe faster or fancier models. But in my opinion, this kind of program is started by locating the system and identifying where the trigger and entry point of the program are. Then you get the full advantage of the program. You don't need to worry about any infrastructure.

I think this is the future. Compared with the EC2, you don't have to pay anything if you don't run it. Otherwise, with EC2 when our client provisions the system and the instances, you always have to pay. There are other tremendous advantages, like flexibility. After you provision EC2 you can write something that does not totally follow the cloud convention. You use it to provision the container. With the program you need to have those 10 principles of cloud computing. Especially recently, within the past four or five years, I have gotten away from DevOps, or the software development life cycle. Even though I researched the product portfolio from DevOps and then the life cycle for DevOps, I try to position myself as an architect with hands-on experience.

In my opinion, Lambda is very similar to Salesforce, which is the original for the SaaS platform and is an extremely low-code environment. With Microsoft and AWS you can say, "Okay. You can choose whatever language you need to make it even more flexible." 

Everything is the cloud. Lambda is a fully managed service. If you want to do it either as a private cloud or on-premise, I'm sure you can do that, too. But I don't know how to manage the pricing structure. But then you've lost the point of Lambda because if you do not use it, you do not pay. Again, I just want to emphasize, I'm not a Lambda expert. But, logically thinking, the big advantage of serverless programming for the customer is that you just use it and pay. Pay and go. You don't need to provision anything.

All my experience with AWS Azure is on the public cloud. We do not get too deep. In IBM we do. When we do sales training we always get the private cloud on-premise. There are many reasons for this. One reason is that IBM lost the battle for the public cloud so we get into it much deeper. We go to the enterprise and we can deploy programs to your data center and offices. But for the tech data for AWS and Azure, we are all using the public cloud as a showcase when we talk to the customer and to the retailer.

The number one feature with AWS Lambda is that it is fully managed. From the developer's perspective, you get the coding much more easily. Now many situations are not using code. You plug in, assemble it, and configure it. Lambda makes it low-code. I come from being a Java certified developer for 15 years. You configure the environment for deployment just like in DevOps. That was always the most challenging part as a developer. You identified when to trigger it. If the program can't facilitate it, then 80% is gone. With 20% you just Lose Syntax. You can use Lose Syntax with any programming language as a reference finding out the variables, the statements, the loop, and what other kinds of things you can do. Just follow that to where you can plot it into your business system. 

They might think to have the business benefits say, "Hey, if you don't like it, no need to pay." So, potentially, you can save. If the future is going to be serverless, that's what I think the future of something like Salesforce will be. Programming is getting much easier and does not need a lot of configuration because step-by-step abstraction starts from the infrastructure service. You can replace your hardware, but you still need to do a lot of things in the abstract. The environment now is totally fully managed. I'm not sure if we're totally aligned there. I always talk against those aspects in the Salesforce situation. But I believe Lambda is a comparable peer, apples to apples.

I can only speak from the user experience. Salesforce integrates SharesPost efficiently. How? They say, "Okay, I invented another language called Apex. Forget about anything else. This is my language." The benefit of this language is that everything is simplified. Your system is super easy to maintain. But AWS then assures you that they are flexible, that they have a collection of 10 or 20 languages, and you just choose your environment and range. That's the reason I appreciate Salesforce. They always make things easier. They have their loop reasoning because they are a different kind of company. Microsoft and AWS really get the full spec. They want to own the business. But Salesforce data wants the simplest way.

So, this is my understanding and unique experience.

I think that perhaps Lambda could explore its functionality more.

I have been using AWS Lambda for a few months.

I didn't explore enough information to evaluate that.

I didn't experience the scalability personally, only from my reading. Amazon takes care of the scalability. That's the right way. It's automatic and it's fully managed. That's one benefit of Lambda.

We have all kinds and sizes of resellers. There are large enterprises and small businesses. It's different. And some of them are product based, they are creating their own products. Some of them are consultant based. It's really different. Tech data is different vs. a business model.

I contacted support many times. My experience was very little and I just saw how Lambda was working, to try to understand if it is okay.

I don't actually use AWS Lambda. I'm a distributor. I try to explain solutions to the vendor. I previously used Salesforce Apex. I use the Azure Logic App service.

Salesforce does not have so many options to choose from, such as Java or C++. Salesforce said, lets invent a language. They call it "invent" but actually they just made a simplified edition of Java and eliminated a lot of complex features. Now all the syntax is the same. Salesforce is a business company. They focus on business solutions development and they make the customer's lifecycle development simple. AWS really does not stick to any business because they are a technology company.

Let me explain the similar things that Lambda has to Salesforce. When you get the event you have to see our form. With the sales approval process, if you have the 50% to get to the half million and above, you need the vice president to get the approval. You can use this trigger based serverless program. All you want to do is to write down the logic and then put it under the trigger of whenever a certain number changes in the half billion, and then you need to do the multiple steps.

This kind of programming is easily defined in the business. All you need to do is get the logic done, get it tested, see the steps you are doing, and then fix up the errors. As for Lambda, as I said, I've just experienced two very simple examples in the AWS, but they were the same thing.

Logic App and Lambda should be doing the same thing - fully managed coding. You focus on the logic triggered by the certain events. And there are other additions within the Lambda family. It can be scheduled as a batch job. I don't think it's originally lack of motivation from the serverless. The serverless is from the trigger.

The initial setup is straightforward. If you follow a 30 or 45 minute lab, it seems pretty clear.

Everybody should check out AWS Lambda. That's why I didn't explore much and it was at the top of my list. This is a fully managed model. The number one. This is for the future. In the future, many of the EC2 applications may be replaced by Lambda. If I started something from scratch, I would try to use Lambda. It's much simpler. It can simplify a lot. If you add the scalability into the picture, it could have 80% or 90% of the complexity. They are very important. All the servlets are very important from a cloud computing perspective.

On a scale of one to ten, I would rate AWS Lambda an eight.

I am a fan of the no-code, low-code if you consistently improve to make it even simpler. Maybe they could do something to simplify the language. I'm not sure if Lambda has the code for the Microsoft Logic App, which means they can eliminate most of the code and everything becomes drag and a drop. Because they eliminated those "if errors." They have those kinds of functions. I think mostly because I have not explored the whole portfolio of AWS. I believe there is a full suite of them.

I believe their full suite of the service is complemented with Lambda. But I do believe the competition is going to make it simple with low-code, no-code. There is no-code, low-code and also no infrastructure. That is going to be the key. Also, maybe you can have the Lambda ecosystem and have some component of the module built above the Lambda so that people can make graphing and plotting even easier. This is not just any software, you get the module there which is much better. But AWS is big enough to neutralize the ecosystem. I believe it will come but the people don't have the patience to start from scratch these days.

We are using the solution for creating the functionality. We store files over S3 and trigger that functionality to deploy our application. We use the solution for serverless activity. Once we store the files inside our S3 bucket, we write specific scripts in Lambda for auto-configuration. Afterward, whenever we send any data inside the S3, it gets automatically picked and deployed in the particular server.

The solution's most valuable feature is its ability to work as a serverless application.

They should work on the solution's stability and pricing.

We have been using the solution for a year.

It is averagely stable.

It is a scalable solution. I rate its scalability as a five.

The initial setup took work. I have worked on the development activity of the solution. The cloud architect of the solution needs to learn Python programming, like coding activities, to update new scripts inside Lambda. It requires a team for the process. I came across some issues during the deployment process and was able to fix them within an hour. So, fixing the problems after raising a ticket while deploying the solution takes time. I rate the setup process as two or three for a medium-level expert. Further, I rate the process as a nine for an executive with knowledge of Python programming. If everything works well, it takes 45 minutes to deploy the solution.

We took help from an Integrator to implement the solution. We were a team of a business analyst, DevOps engineers, and one developer working on the setup. We looped in another person in case we faced any issues.

The solution's price is average, and I rate it as a five for pricing.

The solution doesn't require any maintenance if you are creating an instance on your own. In case of any issues with Lambda services, you can check with their AWS support team. Also, they have provided a support portal inside the dashboard. You can ask for their help. 

AWS Lambda is a good solution. If you are well versed with Linux, AWS will be more accessible. I rate the solution as an eight out of ten.