AWS Lambda Reviews

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.

Public Cloud

Amazon Web Services (AWS)

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.

Less than one year.

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.

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.

Public Cloud

Amazon Web Services (AWS)

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.

Private Cloud

AWS Lambda is primarily used for serverless architecture. I have used it for web applications, particularly during my time at a company where we developed an image processing tool. It helps to trigger events on a runtime basis. AWS Lambda also has various other use cases such as machine learning processes and handling big data tasks.

AWS Lambda's serverless architecture and event-driven programming are highly valuable. You pay only for the events triggered, optimizing costs. It is beneficial for deployment CI/CD tooling and for triggering pipelines for data processing. The cost model is pay-as-you-go, with a tier for free requests and computational time. Scalability and stability are also very efficient.

AWS Lambda could offer support for more programming languages beyond Python and Node.js. The process for creating Lambdas could be simplified for beginners with less expertise in AWS.

I have been working with AWS Lambda for almost eight years.

Deploying AWS Lambda is pretty quick if the process is known. It takes between 30 minutes to one hour to deploy once the code is ready.

AWS Lambda is very stable. Issues are typically related to the user’s code and can be debugged through logs such as CloudWatch.

AWS Lambda's auto-scaling features are crucial for operations and provide great scalability. I rate the scalability of AWS Lambda at eight out of ten.

The documentation for AWS Lambda is comprehensive and thorough, eliminating the need for frequent technical support. A 2000-page guide covers all aspects, from setup to advanced use.

Positive

The initial setup of AWS Lambda can be somewhat challenging for first-time users, primarily due to the learning curve involved. I would rate it a six on the ease scale.

AWS Lambda has a cost model that aligns with usage. There is an initial free tier, after which charges apply based on requests and compute time. Different architectures have distinct pricing models. Despite being a bit expensive initially, the overall cost effectiveness is notable.

AWS Lambda should be used when there is a need for event-driven programming on an as-needed basis. It might become expensive if used for continuous processes. In terms of the overall solution, I rate AWS Lambda at nine out of ten.

Public Cloud

Amazon Web Services (AWS)