AWS Lambda Reviews

We use it primarily for image resizing in batch and scheduled jobs. Additionally, one of our clients relies on Lambda for running a continuously active custom API, handling their ongoing API requests.

Leveraging it to run containers directly from Amazon Elastic Container Registry has proven to be highly valuable. The utilization of containers is particularly beneficial in overcoming the size limitations imposed on Lambda functions which not only allows us to work around these constraints but also contributes to the improvement and maintenance of our code.

There's room for improvement in the testing setup. Attempting to test it through the AWS CLI also posed issues, and when trying to test the Lambda function on my local machine, I encountered difficulties in obtaining comprehensive logs or error messages to diagnose what might be going wrong.

I have been working with it for one year.

It provides a high level of stability, and I have not encountered any issues so far. The system demonstrated stability whenever we attempted to update the function or perform any operations. Responses consistently aligned with the timeframes specified on the AWS website, remaining within the service level agreement. I would rate it nine out of ten.

The scalability is notably high, I would rate it nine out of ten. Approximately sixty percent of my clients are utilizing this approach. While I serve two major organizations, the majority of my clientele consists of small and medium-sized businesses.

The technical support from Amazon has been excellent, and I've consistently had positive experiences. During a customer migration from another cloud provider to AWS, the entire technical team provided valuable insights and enhanced the architecture. Their assistance not only improved the overall design but also ensured smooth transition and support. Even for minor issues, the response times have consistently exceeded the expectations stated on the website. For instance, if a 24-hour response time is indicated, they typically respond within twelve hours. I would rate it nine out of ten.

Positive

I would rate the initial setup around seven out of ten. While it wasn't overly challenging, it did demand a certain level of technical proficiency. Someone without substantial technical knowledge might find it less straightforward to set up.

In our container-based approach, we initiated by constructing containers on the local developer machine, then we pushed these containers to AWS Elastic Container Repository. Following this, we established a Lambda function that utilized the uploaded ECR image, allowing it to execute the associated container. Additionally, we incrementally built services to utilize those containers at Lambda functions. The deployment took less than three hours.

The pricing varies based on the specific solution you're implementing, and in comparison to the value it provides, the overall cost is reasonable. When used appropriately for its intended purpose, the price is relatively low. However, if Lambda is employed outside its intended scope, the cost can escalate exponentially. I would rate it four out of ten.

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.

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

I am using AWS Lambda for building web and mobile applications.

AWS Lambda has helped my organization by making it easier to code and it is less costly.

The valuable feature of AWS Lambda is the ease of coding. It is easier to code using the solution.

AWS Lambda can improve its file system-based sharing capabilities and restrictions.

I have been using AWS Lambda for approximately six years.

AWS Lambda is stable.

The scalability of AWS Lambda is good.

We have approximately 1.3 million users using the application that uses the solution. We have 10,000 to 20,000 new users added every month.

The support from AWS Lambda is good.

I rate the support from AWS Lambda a four out of five.

The initial setup of AWS Lambda is easy. The full implementation took us there to four months.

I rate the setup of AWS Lambda a four out of five.

We did the implementation of AWS Lambda in-house.

We migrated from an on-premise server to the cloud with the Lamda solution and we found it less than one-10th of the cost of what it used to be. We have 90 percent savings.

I rate the ROI of AWS Lambda a four out of five.

AWS Lambda license is paid on a monthly basis.

I rate the price of AWS Lambda a four out of five.

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.

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.

As a platform team, we had to enable a light-weight ingestion platform ensuring the aspects of governance were baked into the platform and the business teams could accelerate their cloud adoption and only develop the business logic.

AWS Lambda improved our productivity and also enabled the business teams to build their ingestion systems at ease.

AWS Lambda's best feature is the lightweight framework that allowed us to bring down a lot of boilerplate code as part of platform capabilities and give the developers an opportunity to only write business-specific logic.

There were some timeout issues with AWS Lambda as the options provided didn't suit our business cases. In the next release, AWS Lambda should include integration with an IoT.

I've been using AWS Lambda for about a year.

AWS Lambda scales really well.

AWS Lambda is cost-effective, with a minimal maintenance cost.

I would rate AWS Lambda eight out of ten.

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.