My advice is to think about the architecture first and don’t just throw your code into Lambda. Think about how your application is designed because using serverless is different.

I would rate this solution as a ten out of ten. It's a very critical service. 

I rate the overall solution a nine out of ten. 

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.

If you have a data application with a huge number of users that requires frequent user interaction, AWS Lambda may not be the best fit. However, it's suitable for applications with less frequent user interaction, like those accessed periodically, maybe every few minutes or hours.

For lightweight applications, AWS Lambda is a ten out of ten.

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.

I would advise others to try the solution.

I rate AWS Lambda a nine out of ten.

Understanding what your use model looks like is the key. All these cloud providers have so many different ways of implementing a solution that you really have to understand the near-term and long-term picture for that solution. What does it look like? When you're first building it, there might be a more expedited way to get it off the ground, but that may not scale properly, or your cost can get out of control. So, it is very important to align the right set of features within an AWS or Azure environment for not just getting the initial MVP built but also making sure that you're building it in a way that allows scaling and optimization of the cost model over time as the application scales. There's no one answer. The way you build the solution in the cloud is very dependent upon what the use case is.

From my perspective, not being at the engineering level, I would give it a nine out of ten. There is always room for improvement, but it has been a terrific advance over what was previously available just having to build everything in EC2.

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.

I would rate the solution a ten out of ten. The solution works fine for us and we didn’t require the need to maintain it. I didn’t face any problems working with the product.

We are a customer and end-user. We use the cloud for integration purposes. 

I'm not completely into AWS Lambda just yet. What I can say, integration-wise, Lambda does not require any username or password from the Jira once they start talking to each other. It's integrated very well. 

I'd recommend the solution to others. 

I'd rate the solution seven out of ten. It is a very new tool for me; I need to do some more research on it to really understand it fully.

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.

I will recommend the product to others. We can automate the processes and integrate the solution with other services. The product provides elasticity and automatic scaling features. Overall, I rate the product a nine out of ten.

The solution can be used for many scenarios encountered by IT developers. There is a general push to create serverless systems that have on-demand use and price models. For most use cases, there is a 50% chance the solution will be a good fit.  

I rate the solution a nine out of ten. 

I would rate this solution a seven out of ten overall. 

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.

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.

I recommend thoroughly reading the documentation to determine if it is a suitable solution for your specific use case. It's essential to understand the nuances of your use case before proceeding with the implementation. Overall, I would rate it eight out of ten.

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

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.

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.

My advice to new users is I would recommend strongly going with AWS Lambda for all API-based solutions.

I rate AWS Lambda an eight out of ten.

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.

I would rate AWS Lambda eight out of ten.

I would rate AWS Lambda an eight out of ten.

I would advise others to use it in those circumstances where it works well and to be aware of the problems with coordination and orchestration. Make sure that it doesn't have to process tons of data.

I would rate this solution a seven out of ten.

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.

I would rate six out of ten overall for AWS Lambda and all the Lambda solutions,. Because we don’t have the solution for each of our use cases. It is not available in various aspects and sometimes, it is not suitable.

I rate the solution a nine out of ten.

If an organization wants to go serverless, Lambda offers a truly serverless service. Even though there are some areas that could be improved, I rate this solution 10 out of 10. 

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 would recommend this solution to others. If you are with AWS it is better to use the serverless architecture.

I would rate AWS Lambda a nine out of ten.

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.

They have a program for AWS customers called Activate. With the Activate program, you can get compute and storage credits. They gave us like $10,000 worth of credit over 18 months.

I would recommend using this solution. It was the first microservice. It doesn't have much overhead, and it does what it claims to do. 

I would rate AWS Lambda an eight out of ten. It is a good solution.

I would rate the tool an eight out of ten. 

I would rate the solution a nine out of ten.

AWS Lambda now supports multiple languages, but find out if the language you want to use to write your jobs is supported by it. If it is supported, then you are good to go.

Because AWS Lambda is scalable and does what it's meant to do, I would rate it at nine on a scale from one to ten.

AWS Lambda is phenomenal with data, and I would rate it nine 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.

I would recommend this solution to others. Overall, the solution has improved since we started using it in 2017. 

I would rate this solution a nine out of ten.

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. 

I'd rate the solution at a nine out of ten. I've been very pleased with its capabilities in general.

I would recommend the solution to other users and companies. 

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.

I would rate AWS Lambda ten out of ten.

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.

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. 

I rate AWS Lambda a nine out of ten.

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. 

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 are an extensively using

I'd recommend the solution to other users and organizations. 

With time-out limitation, it's not a perfect fit for the batch process which takes more than 10 min.

AWS Lambda is user-friendly, people can learn very fast. People should start using AWS Lambda instead of using their own servers. It is very cheap and is the best way where any student can learn.

I rate AWS Lambda an eight out of ten.

I rate the solution nine out of 10. 

I would recommend this solution to others. 

I would rate this solution a nine out of ten. 

I would advise others to predefine the main model and ensure their CI/CD pipeline.

I am satisfied with Lambda, and I would recommend it to others. I would rate it an eight out of 10.

I rate AWS Lambda 10 out of 10. I can recommend Lambda. It's a good fit for our use case. It's also suitable for companies of any size. For example, we're a large enterprise, and we've used Lambda without any problems in the last 10 months.

I would recommend this solution to others who are interested in using it.

I would rate AWS Lambda a nine out of ten.

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.

So far, the solution has been reliable and flexible. Our developers write the code, and we monitor any failures.

I would recommend Lambda to other users and rate this solution an eight out of ten.

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. 

I rate AWS Lambda nine out of 10.  

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. 

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.

I would recommend this solution to others. I would rate AWS Lambda an eight out of ten.

My most important criteria when selecting a vendor are

• user experience
• support.
  

I would rate AWS Lambda at a six out of 10 because it's not quite clear that it scales, but it does have a good, easy path from when you're using a cluster.

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.

I use other products that are in the AWS ecosystem, including AWS WAF.

In summary, this is a good product, it does what it is supposed to, and I recommend it.

I would rate this solution a ten out of ten.

For automation developers, we do not care too much about which CI system we use. It does not affect us too much. Automation tests can be ran in most of mainstream CI systems.

For those who want to use this solution, I would advise them to learn the Python programming language.

I rate AWS Lambda a six out of ten.

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.