AWS Lambda Reviews

AWS Lambda is a serverless architecture. So, you can use three languages like Java, Python, and Node. You can write your code in any language. The main use is if you have a team and your team has one Java developer, one Python developer, or one JavaScript developer. You all want to work together and in a single project, you can use multiple languages, by any of the users.

All of the features are very good and useful.

The most valuable feature for example Java needs a server, so you need to host your application somewhere. AWS Lambda is itself serverless, and it is connected to the API gateway, and you can directly call the API through the API gateway and connect through AWS Lambda.

I would like to see the five zero four AWS Lambda invocation fixed. This is basically a time-out error. Having consistency in this aspect will enhance how robust the solution is for us.

I have been working with AWS Lambda for the past two years.

The stability overall is good. As I mentioned before sometimes you get a couple of time-out errors that need to be fixed.

It is highly scalable. You can use any of the features I mentioned, and you can write a number of functions in one project. We already use around twenty-five functions in one project.

The initial setup is difficult. You need a lot of the code background. You should be at least five to ten years as an experienced developer.

If it is a single deployment it will not take very much time. However, it does take more time as you increase code and volume.

The clients have seen a return on investment.

The price is expensive and is based on usage. The more users you have the higher the cost.

I would rate AWS Lambda 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.

We use AWS Lambda extensively for our maintenance work, for our products, and in our daily actions. We try to move some data based on alerts in certain situations and events. For example, if we are using queues based on the queue methods, we prefer to trigger different Lambdas for different functions (to enable some functionality across products). There are also a few Lambdas for audits. There are a few Lambdas for backups and many other use cases. 

I like that it's easy to use and maintain. Lambda is good and supports different platforms, so you don't need to worry about language or maintenance.

The execution time could be better. One of the major limitations is the time period because it doesn't give you more than seven minutes. So, before thinking about Lambda, you should think through your use case and ensure it's a good fit. Otherwise, you can use batch, step functions, or other methods. 

Reports and the monitoring board could also be improved in terms of alerts. The threshold alerts are there but can be improved. It takes some time to get used to these methods and get the hang of them. 

I have been using AWS Lambda for about five years.

AWS Lambda is pretty stable.

AWS Lambda is scalable. There are some concurrency issues where threshold values play a role. We might end up making a request to increase those threshold values or the limit quota, but otherwise, it's pretty decent.

AWS Lambda tech support is pretty decent. 

On a scale from one to five, I would give AWS Lambda tech support a four.

Positive

The initial setup is more about usage. Implementing this solution takes about 15 minutes, but the code and debugging will take some time. Two or three people can manage and maintain this solution.

On a scale from one to five, I would give the initial setup a five.

AWS Lambda cost is pretty decent. 

I recommend this solution to new users as this tool simplifies mundane tasks and achieves a few things between the two systems.

On a scale from one to ten, I would give AWS Lambda an eight.

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 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.

I've been using AWS Lambda for one year and a half.

AWS Lambda is a stable product.

I have yet to contact the AWS Lambda technical support team because I haven't experienced any difficulty with the tool.

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.

The initial setup for AWS Lambda is straightforward. It's effortless to start using AWS Lambda.

Price-wise, AWS Lambda is very cheap. It's not free, but it's not that expensive.

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.

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.

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.

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.

I have been using the solution for one year.

The solution is stable.

The solution is scalable.

The initial setup is easy but you do need some experience.

The implementation was completed in-house.

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.

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.

I use AWS Lambda for event-driven computing and various other projects that benefit from its serverless architecture.

AWS Lambda supports event-driven computing, which is incredibly beneficial for our projects. Its scalability allows us to handle varying amounts of load efficiently, and it integrates smoothly with other AWS services to enhance our application workflows. 

Additionally, AWS Lambda is cost-effective, providing noticeable cost savings.

I would like to see improvements in AWS Lambda's stability and setup processes, as there were some complexities encountered initially.

I have been working with AWS Lambda for a substantial amount of time.

We have faced some stability issues with AWS Lambda, although it generally performs well.

AWS Lambda is scalable, and we have found its scalability beneficial for our projects.

I have not escalated any significant issues to customer support regarding AWS Lambda, but generally, AWS support is helpful.

Positive

I have experience with other compute services from different vendors, such as Azure.

The initial setup of AWS Lambda was somewhat complex and not entirely straightforward.

AWS Lambda has contributed to cost savings and performance improvements in our organization.

The pricing of AWS Lambda is reasonable, though there is always room for more flexibility.

I have evaluated solutions from other vendors, including Google and Microsoft Azure.

Overall, I would recommend AWS Lambda to others due to its capabilities. On a scale of one to ten, I would rate it quite high - and eight.

Our company uses the solution as a function engine to deploy triggered events for customers. We have a team of twelve developers and our deployments have 1,000 to 2,000 customers during peak times. 

The solution runs on the latest cloud technology so it is easy to deploy cloud-native projects. 

The solution is very useful for managing triggered events. 

It can be a bit difficult to switch between accounts when creating services for customers. 

I have been using the solution for one year. 

The solution is cloud-based so of course it is stable as long as the cloud is available. 

The solution is scalable. 

We have not needed technical support. We utilize available documents that contain content for solving any issues. 

The solution is serverless computing so there is no setup. You just launch the service, write your code, and run it. 

The solution is part of the AWS subscription model that is paid annually. There is no charge for monthly usage. 

There are many calculation criteria for AWS services or licenses. It is difficult to say whether the solution reasonably priced or expensive. Each company weighs price against the benefits and efficiencies provided by the solution. 

AWS is the pioneer of cloud computing and they lead the industry in innovations. Other providers follow in AWS' footsteps to implement similar features and service levels. 

AWS has differentiated the use cases for serverless computing. Lambda is used for basic capabilities like triggered events and Fargate is used for extended capabilities. 

I started using Lambda for a specific use case and I continue to use Lambda and Fargate for use cases as recommended by AWS. 

I definitely recommend the solution and rate it a ten out of ten. 

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.