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. 

Usually, it is for small transactions. They're very atomic transactions. For example, we built a solution for an ad platform where an electronic ad runs for about 15 seconds a piece. Every time one of the ads runs, we have to record where did it run, how long did it run for, who was in the room, and how many people. There is a bunch of data around that. We typically send that transaction through an Amazon Kinesis pipe into a Lambda function, and then Lambda will take it and store it in S3 or target it to Redshift or put it in some kind of data store. That's one example of what we would use it for. That's a typical model for Lambda. 

It is serverless and scalable. It can scale infinitely. You don't have to worry about the size of the servers that you're pre-allocating. You don't have to build server scale-out models. Auto scale and other similar features are just inherent in Lambda. So, for atomic and fairly non-persistent transactional units of work, Lambda works very well.

My engineers work with it on a daily basis. I just don't have enough depth of knowledge about what kinds of edge cases they may have tried and found lacking. There may be some issues with some language support at one point or another because we couldn't get the underlying libraries in there. A lot of what we do is either in JavaScript, Python, or some of the non-compiled languages. I'm not sure if we've ever tried building a C# solution, for instance, in Lambda or a Java solution in Lambda. It doesn't mean those aren't its capabilities. I would rather refer to my engineers for where the boundaries are.

It has probably been five or six years since we've been migrating functionality from EC2 instances to Lambda.

Its stability is really good, and it is also highly available. The stability is inherent, but it also naturally gives you a high availability model because you don't have to have multiple EC2 instances running in, for instance, different regions. It is baked into the model. So, you can allow for inter-region Lambda functionality. It all becomes very highly available across Amazon's footprint.

It is endlessly scalable. In terms of its users, Lambda is typically baked into the middle of an application somewhere. Our ad platform solution is a fully-automated IoT solution. So, there are no people involved. The whole thing is automated from end to end. So, sometimes people don't even come into the equation.

We probably do or have dealt with their support, but that would be at the end engineer level. It is not something to which I would have much visibility. 

It is straightforward in my understanding. From the engineering perspective, I haven't gotten feedback that it is at all burdensome.

You're not paying for a server if you're not using it, which is another reason I like it. So, you're not paying if you're not using it. It scales, and you're charged based on usage. It all depends on the use case. Some can be extremely inexpensive if you have very low volume transaction rates. That way, you don't have to fire up and absorb the cost of the servers just sitting there waiting for a transaction to come through. You're only paying when you use it. So, depending upon the use model, Lambda could be highly efficient relative to an EC2 solution. You don't have to have things reallocated.

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.

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 are building a Twitter-like application in the boot camp. I have used Lamda for the integration of the post-confirmation page in the application. This will help you get your one-time password via mail. You can log in with the help of a post-confirmation page. We didn’t want to set up an instance specifically for confirmation. We used the Lambda function so that it goes back to sleep after pushing up.

The tool changes its UI every month which is very frustrating for me. I don’t know why AWS keeps changing the UI. They can’t stick to a specific one.

I have not faced any stability issues with the tool.

I know that AWS has flexible support but if I encounter any problem, then I just Google it. I get a lot of support from Google, YouTube videos, and Discord channels.

The solution’s initial setup was neither easy nor complex. I started learning about cloud services about six to seven months ago and already had a background in it. However, the implementation was not easy since a lot of errors just popped up. I had to check the CloudWatch logs and look into the bugs in the code. It wasn’t interesting. The deployment took around two hours to complete.

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 primarily use the solution for integration purposes. We use it very closely with Jira, for example. 

The workflow is the best thing about the product. When the integration happened and from where to where is something we can see automatically and navigate the workflow. 

From Jira to AWS Lambda, we're sending data. When we go from Jira to AWS, through webhooks, we are sending data to the Lambda function. From Lambda, they're navigating Jira. Whenever the manual rework is done, they need to perform some job bundles from the AWS to the Jira only. They can operate from Jira to AWS and AWS to Jira, which is great.

The initial setup is pretty easy. 

I don't have much experience after six months. I can't speak to the pros and cons. 

I have seen some drawbacks with certain integrations. 

I started using the solution six months ago. 

I'm not aware of any issues with stability. It's been issue-free so far. 

The solution can scale. We can add more users to it. We have ten to 15 people on the product right now. They are developers. 

I've never needed to reach out to technical support. I haven't had any issues. I can't, therefore, speak to how helpful or responsive they are. 

We found the setup to be straightforward. It's not complicated at all. 

It took me one day to get everything up and running.

I'm not aware of the exact pricing. I don't handle any licensing. 

Our company is looking into ServiceNow to see how it handles integrations. 

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.

I have found this solution very useful. By using Lambda, we can use Python code and the Boto3 solution. 

The triggering feature is also valuable. For example, if we are using Kafka, we need to be aware that the language comes in Kafka when we write in Python, and that we are transforming our data into the meaningful server and dumping that into the S3 bucket.

I would like to see a find and replace function as part of Lambda's future releases. Currently, if we want to replace a code, we copy the code into Notepad, then find and replace it, and then copy that to Lambda. This would improve the editing function of the product.

Lambda would benefit from a debugging feature as well. For example, if you want to debug code running in Python and deployed in Lambda, it would be beneficial to have a debugging feature.

I have been working with AWS Lambda for one year.

The solution is stable. There are times when we do need to refresh when we make changes and deploy them. This seldom occurs.

We have five developers using Lambda. 

Technical support can take a long time to respond. I would rate their service a seven out of 10.

Neutral

The initial setup of AWS Lambda is simple.

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

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.