AWS Lambda Reviews

I back up my MongoDB, that database has user data. The performance of AWS Lambda has been fine.

It has made things a lot easier in terms of restoring if we need to and just not having to worry about the small things.

The console is very good, the user experience works very well.

I would like to see some better integration with other providers, like Cohesity, Druva, and others. I also think the Lambda interface could be better.

I don't have a ton of transactions, so it's very stable from my perspective. But I can imagine that it would not necessarily be as great for an enterprise product.

The scalability is hard for me to see from where I sit because I have a very small company, but I can imagine that it's going to be an issue.

Tech support is very minimalist. It's more do-it-yourself, which works for me, but I don't think it will work forever.

The setup was pretty complex because there were many steps. For me, it was complex because I was somewhat new at it. It could be easier for someone who has done it a bunch of times. I just found that it was a very dense user experience. There's a lot going on during setup.

The vendors on the shortlist now would be Cohesity, Commvault, Druva. But in the past, I went with this because we were using an AWS cluster anyway. It was easy-ish.

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 have some APIs and we use some mechanisms to process these APIs. Normally, some APIs need to be hosted by some servers. However, with this product, we can compute everything serverless.

The solution is designed very well. You don't need to keep a server up. You just need some router to route your API request and Lambda provides a very well-designed feature to process the request. 

From our perspective, the solution works for a variety of scenarios.

It's very straightforward and very easy to use. We don't need to keep several apps. We just use some APIs and to route with the APIs to create related Lambda functions.

The kind of scenarios we can leverage in Lambda can be difficult. For example, we have a lot of their servers that provide APIs. Before, the APIs were hosted by a server. We have identified that some of them can be hosted in Lambda. That's a challenge as we're yet to think of our scenario and match our requirements in order to really leverage Lambda. That's more on us than the solution itself.

We need to better understand Lambda for different scenarios. We need some joint effort between Amazon and the users to have the users identify how they can really leverage Lambda. It's not about Lambda itself; it's about the practice, the guidance. There needs to be very good documentation. From the user perspective, what exists now is not always enough.

Lambda is stable. We don't see any problems so far. There haven't been bugs or glitches and it doesn't crash or freeze on us.

The solution is very scalable. We just allocated a very small number of requirements to Lambda. We've still found it to be very scalable.

We are a technology company, so we do not have many users. Most are developers, engineers, and architects.

So far, we've found the technical support to be okay. They are knowledgeable and responsive and we are satisfied with the level of support we get.

The initial setup's level of difficulty depends on different requirements. Normally, we can see that number to process and do a straight comparative analysis for a simple scenario. The deployment is fine for the most part. We don't spend much time on it in comparison to a traditional deployment. It's very quick.

When you try some services, with Amazon, the first phase is okay. When we continued with more workloads placed on Amazon, we needed to take into account the cost, as the cost to the firm becomes more and more. It can get expensive if you aren't careful.

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.

AWS Lambda is a Code as a Service product. It is used for running code.

This product is easy to use.

The integration with other AWS products is straightforward. For our current usage, the integration that we have is sufficient. Everything is connected to CloudWatch and it's working.

I have been using AWS Lambda for one year.

AWS Lambda is a stable product.

This is a very scalable solution.

At this time, we don't anticipate increasing our usage.

The technical support is great.

The installation is straightforward and it only takes a few minutes to complete.

I deployed it myself.

This is a product that is pay-per-use, as opposed to a licensing fee. It could be cheaper.

There are no costs in addition to the standard pay-per-use fees.

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.

1. Use lambda function to trigger the jenkins jobs to make whole release pipeline.

2. Send the slack notification once the release with automated test is done.

My automation test story is we moved from CircleCI to Jenkins, then to AWS. The benefit I can see is the maintenance and budget. Ops made this decision but it did not affect automation tests and the release pipeline too much, but I have seen the release pipeline has been developing much faster.

We use AWS Function and Jenkins API to trigger the Jenkins job from the AWS CodePipeline.

Since our automated deploy jobs are on AWS, and automated tests are on Jenkins.

Then we can create the release pipeline including AWS and Jenkins and put them together.

1. Cannot checkout code from GitHub but Jenkins can.

2. No shell script supported.

3. CodePipeline cannot send notification to Slack, but we can use Slack API and Lambda Function.

Pretty good.

I saw Ops setup the automated release jobs faster in AWS than in Jenkins and CircleCI.

For automation tests, it does not affect too much. 

Our Ops are all AWS experts.

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.

I am using AWS Lambda to set up real-time notifications and backup transfers.

AWS Lambda could improve by having no-code or low-code options because currently, you need to be able to write code well to use it.

I have been using AWS Lambda for approximately two years.

AWS Lambda is a stable solution.

This solution is best suited for medium to large-sized companies.

I am satisfied with the technical support.

The setup of the solution was simple.

The implementation of the solution was done by my colleague.

The price of AWS Lambda is priced very low.

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.

We have only used it for a few services. It's still in POC mode. We haven't done any production on it currently. 

The most valuable feature is that it scans the cloud system and if they are any security anomalies it triggers an email. 

The running time of AWS Lambda runs fine. It takes around five minutes but it would be great if that time could be extended. 

I have been using Lambda for two to three years. 

We haven't seen any issues regarding stability as of now.

It is easy to expand the platform.

Their technical support is quite good. We have enterprise support, so it is quite good.

The initial setup is easy. 

I did the deployment with the help of consultants. 

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.