AWS Lambda

(35)
4.5 out of 5 stars

Run code without thinking about servers. Pay for only the compute time you consume.

Work for AWS Lambda?

Learning about AWS Lambda?

We can help you find the solution that fits you best.

Find the Right Product

AWS Lambda Reviews

Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • Industry
Ratings
Company Size
User Role
Industry
Showing 36 AWS Lambda reviews
LinkedIn Connections
AWS Lambda review by <span>John B.</span>
John B.
Validated Reviewer
Verified Current User
Review Source

"Python AWS Lambda"

What do you like best?

The ability to run a serverless python function that can interact with other AWS servers is incredibly powerful. Access to the boto3 library allows you to create an application without the need to manage a virtual machine. It is very easy to get started, cost effective and easy to manage going forward without the overhead of additional infrastructure costs and management of the infrastructure.

What do you dislike?

The UI before the recent facelift did not have a great user experience however since AWS devoted time to make the UI better this AWS application is much easier to use. The debugging experience could be better however there are way to improve this by using code modules as well as mocking frameworks.

Recommendations to others considering the product

AWS Lambda is one of the best products AWS has at the moment. Easy to get up and running as well as a variety of other languages you can use to create your functions. Debugging functions locally can be difficult however creating a module that the Lambda functions calls can help with testing your code.

What business problems are you solving with the product? What benefits have you realized?

AWS Lambda, along with API Gateway, allows you to create a simple REST API with very little effort. Lambda scales very well under load and allows you to interact with a database to persist data. It is also incredibly cheap to run and manage; the overhead to manage Lambda functions is at the code level and not at the infrastructure level which tends to take more effort over time compared to managing your code..

Sign in to G2 Crowd to see what your connections have to say about AWS Lambda
AWS Lambda review by <span>Rich W.</span>
Rich W.
Validated Reviewer
Verified Current User
Review Source

"Super easy and incredibly cheap"

What do you like best?

Simple to use product. Incredibly reliable, we've never had an outage. Amazingly cheap, good to know all that spare ec2 capacity does not go to waste! Infinitely scalable. Free for 12 months and very healthy discounts available for accelerator programs. Ability to configure environment variables and test on the console is very useful. Hooks up perfectly to other internal aws products such as rds and elastic beanstalk

What do you dislike?

I don't think the recent UI update is an improvement. May look better but the ux is less intuitive than before. Cron schedule expressions do not take the second argument which is unusual and can cause confusion until this is learnt. Deployment could be streamlined, aws should develop their own service like serverless js. Logging could be improved, ux on cloudwatch is not the best. VPN and security group setup is not for the faint hearted, you really need to know what you are doing here. Timeout of 5 minutes is too short for some applications we have wanted to use it for! Docs are not as clear as they could be.

Recommendations to others considering the product

Its an excellent product, I would recommend a completely server less architecture. Try serverless if you are a node.js user

What business problems are you solving with the product? What benefits have you realized?

Originally used as a tool to fire functions on regular intervals (a tricky and unreliable thing to do on an elastic beanstalk instance) we now moving towards a serverless architecture as it is so easy to use. Scheduling has allowed us to run regular task functions.

What Cloud Platform as a Service (PaaS) solution do you use?

Thanks for letting us know!
AWS Lambda review by <span>Austin C.</span>
Austin C.
Validated Reviewer
Verified Current User
Review Source

"Lambda is excellent"

What do you like best?

simple concept implemented in a straightforward way that eliminates much of the setup pains and leaves most of the flexibility of writing your own code.

What do you dislike?

Metrics and analysis are very difficult and there's not much built-in support.

Recommendations to others considering the product

Lambda is fantastic if you need lightweight, extremely scalable compute. If you need heavy duty long-running computation systems, then lambda is less likely to work for you. If it's an async type long-running system, then you can use step functions with lambda to achieve that in an incredibly simple way, but long-running compute activities don't tend to fit with the lambda idea very well.

What business problems are you solving with the product? What benefits have you realized?

We have written new applications in a serverless system using lambda for the core processing functions.

AWS Lambda review by <span>Gopika J.</span>
Gopika J.
Validated Reviewer
Review Source

"AWS Lambda Review"

What do you like best?

AWS Lambda lets you write and run code in a number of different languages without having to provision resources/servers. I find it very useful to run one-time or event-driven code that reacts to changes in my AWS environment via SNS notifications and logs everything to CloudWatch. Very powerful and cost-effective.

What do you dislike?

If you are interacting with other AWS services, then you need to know how to use the boto3 API in your lambda function. It will be very useful if there is IntelliSense for use of the same.

Also, it would be nice to have a way to easily upload custom packages, include and call them in your Lambda function.

Recommendations to others considering the product

good for small quick execution only

What business problems are you solving with the product? What benefits have you realized?

I use it to automate many things in my environment.

E.g. when team member releases new CloudFormation templates in S3 bucket, it triggers SNS notification which triggers Lambda function that has code to launch Stacks and add to SQS for testing

AWS Lambda review by Administrator in Internet
Administrator in Internet
Validated Reviewer
Verified Current User
Review Source

"AWS Lambda Serverless architecture"

What do you like best?

Lambda is a great way to build applications that scale. It allows you to provide functions in the cloud without the need to deploy and maintain servers.Instead of hosting these functions on a server, you add them to Lambda and then call the function - AWS takes care of the rest.

Its a really great way of reducing costs as by far the biggest cost on AWS is running EC2 instances.

What do you dislike?

Because you no longer need to run a server you also no longer have much control over the environment. There is also the problem of calling the function in a so called 'cold' state, this means the first call will always take longer to perform, and while there are way you can keep the function in a 'warm' state, it adds to the overall cost.

Recommendations to others considering the product

While there are some tradeoffs to consider when heading down the road of serverless applications, I believe the pros outweigh the cons. AWS Lambda allows you to deploy code without the restrictions of server architecture and allows you to vastly reduce the costs of running the application in the cloud.

What business problems are you solving with the product? What benefits have you realized?

Running functions through Lambda means server cost savings - running an instance 24/7 can get expensive. Lambda is only called on-demand and you only pay for what you use.

Putting functions in Lambda also means you get large scale right from the beginning as you are not sending all calls to a single server.

AWS Lambda review by <span>Glenn J.</span>
Glenn J.
Validated Reviewer
Review Source

"AWS Lambda is great for serverless processes"

What do you like best?

AWS Lambda supports a number of languages so I can write my lambda code in whatever language I feel comfortable with. The pricing model is also very good.

What do you dislike?

AWS Lambda can take sometime to figure out. You don't have an unlimited amount of time to run your function so make sure you keep the time require to execute your function short.

Recommendations to others considering the product

Check to see if your favorite language is supported y AWS Lambda and if it is give it a try. I would also read as much documentation as you can before starting with it.

What business problems are you solving with the product? What benefits have you realized?

I have a number of business items that need to run many times during the day based on various triggers, AWS Lambda was the best way to get these to be run and I didn't need to pay for or setup an EC2 instance to do this work. AT this point in time, I do not use it but will start up again soon.

AWS Lambda review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Serverless Deployment + Seamless Services : Lambda"

What do you like best?

There are a million amazing things to speak when it comes to amazon lambda. To begin with, imagine you have some code, maybe multiple API calls, or the chatbot needs to redirect the NLP data to Alexa, but you do not know all the configurations that need to be done, with deployment as well as connections configuration. And here comes lambda, a code that can manage multiple tasks for you. For example, you have your participant's data in the S3 bucket. Now, as soon as the participant submit'ss his file(let us say a sketch) into this folder, a trigger calls your lambda function. Here, the hero enters and save the day by doing whatever is necessary. If you want, your lambda function can point to an AWS SNS service that tells the user in an email that his entry has been successfully submitted. And with that too, it can perform some simple tasks like uploading the data to the judges folders, or complex tasks like performing an image analysis, and finding the desired result on the basis of ML decided. You can configure and limit it to the users who can access it, how much memory it can take, and what triggers are connected to and from it. It is amazing awesome , the only thing you need to be careful with is the Access key and token secret.

What do you dislike?

The first and foremost thing that I did not like is the documentation that AWS had done for the eclipse plugins, hence same goes for lambda as well. I had a hard time trying to figure out ways to do things in lambda all by myself or Stackoverflow. Along with that, the UI for lambda is good, but not suggestive and has no intellisense kind of technology supporting it. It would have been amazing if, as soon as I upload my code, amazon lambda would automatically do the predicted configuration based on my code, like finding and setting up the handler method, etc.

Recommendations to others considering the product

If you plan to use lambda, probably you should look for some tutorial, or wander in stackoverflow, the documentation can only guide you to installing the aws-sdk. Then, you're all on your own.

What business problems are you solving with the product? What benefits have you realized?

Using AWS lambda, we are loading implementing the below mentioned scenario in agile:

There exists and API that loads data into the back-end, i.e. weblogic coherence from a csv file. So, as soon as a file enters the S3 bucket's desired folder, the lambda function is triggered. This function invokes the API with the file url as a parameter, but before that. All validation and data-analysis have been performed by the lambda function on the data in the file so that the API gets neat data to process and input into the cache/database.

AWS Lambda review by <span>Duncan H.</span>
Duncan H.
Validated Reviewer
Review Source

"transactional freedom"

What do you like best?

Used as part of restful api setup, Lamda's were great for functions with short execution times.

Not having to provision servers yourself was a huge leap forward for us.

What do you dislike?

Sometimes when we needed to some slightly more heavy lifting, like downloading or updating large amounts of data, we have to find work arounds. This is fair enough, but just something to be aware of.

Recommendations to others considering the product

Its great for code with short concise responsibility, but be careful as the timeouts are short and large data processing should be moved off into a secondary service for processing.

What business problems are you solving with the product? What benefits have you realized?

Solving the need to setup and manage our own infrastructure. The speed we got code to a production environment was increased, allowing us to focus on the code rather than servers.

AWS Lambda review by <span>Edward M. V.</span>
Edward M. V.
Validated Reviewer
Review Source

"Get started quickly with Python on AWS Lambda with "Chalice""

What do you like best?

If you're considering AWS Lambda, you should look at "Chalice", a microframework for Python that's very much like Flask.

With Chalice, you are carefully guided through the process of setting up your first microservice in Python. It comes out of the box with sample code to do a “hello world” service, and from that sample code the entire set of Lambda packaging is built for you. There are a surprisingly large number of moving parts to actually get a Lambda function running; Chalice’s build system hides most of those from you at the start.

Lambda's best feature is the ability to set up a microservice and run it without running your own server. This looks promising for small to medium scale processing needs that are sufficiently bursty that provisioning your own server would either be overkill (because your loads are too low to justify $15/mo minimum ticket) or underkill (because the $15/mo server would be overwhelmed one hour a month, and you can't justify 10x compute for that one hour).

What do you dislike?

Like all AWS services, Lambda leads to vendor lock-in. Building a complex system on top of Lambda means you are putting yourself at risk of not being able to move off of AWS in the future without a lot of complex development and special server development.

Recommendations to others considering the product

Rather than writing raw Lambda code, use some kind of serverless framework that encapsulates Lambda. That will give you a better chance of portability to another system should you need to move.

What business problems are you solving with the product? What benefits have you realized?

The problem to be addressed is building a service platform that can be inexpensive to run while in development mode and that scales up gracefully.

AWS Lambda review by <span>Murtaza K.</span>
Murtaza K.
Validated Reviewer
Verified Current User
Review Source

"Go Serverless with Lambda Functions"

What do you like best?

In AWS Lambda, you've the option to write necessary code with respect to your needs in your desired language. And best option is to integrate it with AWS API Gateway which enables your Lambda function to be exposed by REST

What do you dislike?

Memory Management is not that much strong and needs tuning by AWS. Deployment options can also be improved using the AWS Deployment Services(CodeDeploy, CodeCommit or CodePipeline) Otherwise everything is good.

Recommendations to others considering the product

If you want to go serverless and need AWS as your infrastructure than AWS Lambda is an option for you. It can easily work with other AWS services like NoSQL, Stream etc.

What business problems are you solving with the product? What benefits have you realized?

I have used Lambda Functions with Big Data's so called "Lambda Architecture" where in Batch Layer I need to execute a Job over the S3 files which is synced from Kinesis stream using Kinesis-S3 Connector.

I've also used it in API gateway where I need to implement a REST Service to provide some third party confidential data and aggregate it with some business logics.

AWS Lambda review by <span>Dave N.</span>
Dave N.
Validated Reviewer
Verified Current User
Review Source

"Really is revolutionary"

What do you like best?

When Lambda was anounced at AWS re:invent, I heard many people describe it as a game changer. Having now used it for a few tasks, I can confirm this is correct. The price for the value it offers is so incredibly cheap and it's very easy to use.

Supporting multiple languages (we have functions in both node and python) makes it very flexible where anyone could use it from a seasoned software developer to a sysadmin with scripting capability.

Being able to have multiple versions of code and switch between them while running tests on a version is a helpful feature as is the built-in monitoring of executions Vs failures.

What do you dislike?

Monitoring of failures could be improved. We had to craft a custom solution to take into account the error rate over the number of executions rather than just a flat "notify me when there are 10 errors".

Being able to send logs to an external log service easily would be handy. The built in cloudtrail logs is really lacking compared to tools like loggly and Papertrail.

Recommendations to others considering the product

Think about more than just writing the code. How will you deploy it? How will you monitor it? How will you get log data from the function(s)?

Look at frameworks like serverless.

What business problems are you solving with the product? What benefits have you realized?

For us, it is being able to run code without having to run servers and other infrastructure. For example, we replaced a simple web app in PHP that polled a queue and wrote data into a database with a single Lambda function. This allowed us to use the server for something else and the Lambda costs is fractions of a penny!

AWS Lambda review by <span>Marc S.</span>
Marc S.
Validated Reviewer
Verified Current User
Review Source

"AWS Lambda is the future"

What do you like best?

First & foremost, the simple fact of taking servers/server management out of the mix is invaluable - especially for someone like me, a developer, who doesn't want to get wrapped up in the operations side of things if i don't have to.

What do you dislike?

Well, there's a little bit of a learning curve in running arbitrary executables with Lambda. You have to launch an actual AWS instance (and a particular one, at that...more or less), and compile the binaries (and possibly related libraries) that your project requires. You then have to include those in all the right places with your packaged up Lambda code.

It would be nice in the future if Lambda expanded the number of available libraries out-of-the-box (e.g., like they do with ImageMagick).

What business problems are you solving with the product? What benefits have you realized?

Using Lambda to run some OCR functions on documents that are stored up on S3.

The simple fact that i'm no longer provisioning a server environment(s) has saved me money, but just as importantly has saved me time.

AWS Lambda review by <span>Julius Aniceto C.</span>
Julius Aniceto C.
Validated Reviewer
Verified Current User
Review Source

"For network automation tasks this is a god send. But for serverless development, lacks tooling."

What do you like best?

The ability to schedule tasks using SQS. Previously I had to write custom cron jobs in a worker instance and maintaining them has become a pain. With Lambda you know exactly when and what functions will be executed.

What do you dislike?

It's difficult to integrate the coding to existing CI/CD products.

The startup time/lag can be large at times. This needs to improve.

Recommendations to others considering the product

Language choice is limited. I've only used Javascript on it, but if you want to write arbitrary code based on events and you don't want to worry about running additional servers, try Lambda.

What business problems are you solving with the product? What benefits have you realized?

We are using it to execute scheduled tasks such as cleaning up SQS queues, triggering S3 backups.

We also use it for a client's serverless backend. We wrote an application entirely on Lambda and API gateway so we won't have to worry about scaling and maintaining servers.

AWS Lambda review by User
User
Validated Reviewer
Verified Current User
Review Source

"AWS Lambda "

What do you like best?

Lambda in conjunction with serverless architecture is a strong part of the future of the cloud. It is easy to scale, don't have to worry about availability, and is much cheaper than running a EC2 server.

What do you dislike?

Logs and debugging can be hard - especially if there are dozens if not thousands of function invocations

Recommendations to others considering the product

If you're looking for functions as a service, AWS Lambda is the way to go! It is easy to use, powerful, and gets the job done.

What business problems are you solving with the product? What benefits have you realized?

Serverless architectures- handling sporadic API calls that saves costs by not having a server run 24/7

AWS Lambda review by <span>Harmandeep S.</span>
Harmandeep S.
Validated Reviewer
Verified Current User
Review Source

"AWS Lambda"

What do you like best?

It's a serverless technique to manage your application.

You could hook it up to cloudwatch, logs and other aws services for advanced functionalities

What do you dislike?

It does not have support for C or C++ programming languages.

Recommendations to others considering the product

If you're looking for a smart ease of initial setup platform then AWS lambda is for you

What business problems are you solving with the product? What benefits have you realized?

Application development and the software which sits on the cloud platforms

AWS Lambda review by <span>Ernesto M.</span>
Ernesto M.
Validated Reviewer
Verified Current User
Review Source

"Could not be easier to get a mobile backend up and running"

What do you like best?

The integrated monitoring features, the way that lets me assess my application's performance at a fine granularity.

What do you dislike?

The .zip workflow for uploading functions, lack of support for newer versions of Node, lack of support for languages other than Java, Python, and JS.

Recommendations to others considering the product

Hard to argue against giving it a spin. Write one or two functions that traditionally go in a Rails controller or Express middleware, you'll see.

What business problems are you solving with the product? What benefits have you realized?

Media-rich group chat.

The benefits have been numerous. I don't spend any time provisioning EC2 instances, configuring OSes, etc. The service also helps guide the development of the app towards a robust microservice architecture. Finally, Lambda + the API gateway means that one set of functions powers any client, be it Android, iOS, or a browser.

AWS Lambda review by User in Internet
User in Internet
Validated Reviewer
Verified Current User
Review Source

"AWS Lambda, low cost server-less service!"

What do you like best?

Low Cost: it is really awesome that I can setup a reliable scheduling and email messaging service which cost only few cents per month.

Server-less: it is really fun and interesting to shift the programming paradigm to server-less architecture. It does require some effort to get familiar with it, but at the same time, it is some thing really interesting to learn.

What do you dislike?

I was using python with AWS lambda, the package setup is bit different from the standard python package convention. Deployment is also a bit tricky.

I'd hope Amazon provide better libraries for setting it up as well as deployment.

Recommendations to others considering the product

AWS Lambda is something I think all developers should have a play with. It is also a great start point to get familiar with other AWS services such as CloudWatch, DynamoDB, S3 etc.

What business problems are you solving with the product? What benefits have you realized?

I created a small script to check currency rate for me, if the currency rate is above certain level, the service will inform me through email (AWS SMS).

- it is interesting to learn how other AWS services linked together with Lambda, and how they can utilised to solve problems. For example, the scheduling is enable through AWS couldwatch instead of using corn or scheduling libraries.

- however, it would be nice if we could programatically associate other AWS resources with lambda instead of configuring it through AWS console.

AWS Lambda review by Administrator in Computer Software
Administrator in Computer Software
Validated Reviewer
Verified Current User
Review Source

"Excellent experience scaling my Node.js Infrastructure"

What do you like best?

AWS Lambda is perfect for integrating into an existing application or for creating the backbone of a serverless tech stack. Initially, Lambda costs virtually nothing and the prices are relatively affordable as you scale. I highly recommend it if you're planning to leverage other AWS services like S3, ETS, etc...

What do you dislike?

The only area it's lacking is in documentation and that can be said for a lot of AWS services. Last time I checked, there wasn't a lot of documentation for getting new users up-to-speed. Fortunately, more developers are adopting it every day, so there are a ton of tutorials online.

Recommendations to others considering the product

I wouldn't recommend diving straight into the AWS documentation unless you're already familiar with the AWS way of doing things. Also, if you're someone who learns by doing, find some tutorials online rather than digging through AWS documentation.

What business problems are you solving with the product? What benefits have you realized?

When working on a production application, finding the right balance of predictability, scale, and cost efficiency are critical if a platform is to succeed. AWS Lambda has provided the right combination of all three.

AWS Lambda review by User in Information Technology and Services
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source

"Code apps not servers"

What do you like best?

AWS Lambda provides me with peace of mind knowing that everything I build on it will be reliable "forever". This allows me to apply it for small projects where maintaining servers would be time prohibitive. Compared to other modern server abstractions like Docker the focus on code over infrastructure requires a refreshingly short learning curve. The potential cost benefit for infrequently used functions is as revolutionary in my option as EC2 was at it's inception. Having the ability to deploy new code without worrying about orchestration, networking, etc, allows me to try new ideas quickly and create rich services with little to no costs for backend services. It really changes the scope of what I can do on small websites with the ability to scale massively under load as needed. Being able to start hundreds of instances of my code for a few seconds allows for the performance of a large EC2 cluster for seconds at a time instead of hours.

What do you dislike?

As with all Amazon Web Services products working with AWS Lambda does result in some vendor lock-in and requires training that is not very applicable to other systems such as OpenStack. Although in my opinion Amazon is the most innovative and "standard" player in this space the community compared to something like Docker is very small. If AWS Lambda were built on a "standard" like Amazon Elastic Container Service is built on Docker then it would be easier to migrate to another service and apply the knowledge to other platforms. Currently the inability to reserve Lambda runtimes to have cache warmed "instances" limits response times, especially for infrequently called lambdas. The deployment process also requires either a high amount of tooling with something like Serverless, or a slower manual upload through the AWS console.

Recommendations to others considering the product

Consider using tools such as Serverless which allow you to more easily deploy functions and integrate them with API Gateway and other event sources.

What business problems are you solving with the product? What benefits have you realized?

I have used AWS Lambda for many work and personal projects of mid to small size. One such work project was a customer payment information update system. It consists of an AWS API Gateway webhook endpoint which receives payment failure events. It then renders and sends a templated email to the customer with a link to a payment info update form. When the form is submitted it is posted to another Lambda function which attempts the payment and notifies the customer in another email if it was successful or not. On successful payment our accounting staff is also notified via our help-desk system. This kind of thing would normally require me to maintain a separate server for "internal" apps which would have limited availability and require constant patching while costing a lot more. (can't beat free) AWS Lambda allows me to code it and forget it by taking the large burden of high availability and orchestration on at a very low price.

AWS Lambda review by Consultant in Computer Software
Consultant in Computer Software
Validated Reviewer
Verified Current User
Review Source

"AWS lambda is awesome, cost effective and scalable"

What do you like best?

I really like the ideia of hosting microservices and pay pennies for millons of requests, and it is also fits really well in the AWS product stack. The integration with CloudWatch is amazing, and the versioning is very good too.

What do you dislike?

I wish it was easier to test and debug them in my own machine, I am currently using the Serverless (http://serverless.com) framework to make this job easier, I think Amazon should deploy their own solution, like Serverless, to make things better. Serverless is very good, but when you have to integrate with other AWS solutions like Cognito, things get a little harder that they should be.

Recommendations to others considering the product

Do use it! Don't be afraid of getting locked up in the AWS stack, the only way to get locked up is if you don't have a good architecture. Use the all the AWS Services as thin wrappers and you will be on a good track.

What business problems are you solving with the product? What benefits have you realized?

I am building an entire application in a serverless architecture, it is the most cost effective way of taking advange of AWS Stack. Very scalable and easy to deploy, using AWS Cloud Formation. The app I am currently building has a Database running on DynamoDB, a push service using SNS, an image resizer (Lambda), an API that uses the combo API Gateway + Lambda Microservices and also user authentication using Cognito. I am very confortable with AWS Stack, I belive in good architecture to prevent being locked up with AWS Stack

AWS Lambda review by User in Financial Services
User in Financial Services
Validated Reviewer
Verified Current User
Review Source

"Serverless scalable solution"

What do you like best?

The pricing. This allows me to create code that doesn't run often but I only pay then is used. Usually I need to use Elastic Beanstalk to keep microservices running.

I like that supports node, python and java. I would love to see other options like C#.

I also saw that I can use with Amazon SES to process incoming mails, I haven't had the chance to look at it but its definitely something I'll use.

What do you dislike?

I still need to master the process of deploying changes. I'll like to have this integrated to git or another solution. Also I would like to have PCI compliance here.

I don´t like that has a request limitation since eventually will prevent us from scale, although it says that that number is increased over the use, it doesn't happen instantly if I need to.

What business problems are you solving with the product? What benefits have you realized?

I like the idea of having microservices. I use it with API Gateway so I create code that I use as a callback. This simplifies the process and infrastructure. I haven't used it for anything critical yet.

The cost is one of the most important points since I mentioned earlier I can run the same microservice in API Gateway+Lambda for a few cents a month versus having a Elastic Beanstalk setup to solve the same need.

I also use it for log analysis. I subscribed one lambda function to be executed each time that a new file is added to a specific folder (ELB logs in my case).

AWS Lambda review by Consultant in Internet
Consultant in Internet
Validated Reviewer
Verified Current User
Review Source

"Not impressed with GraphicsMagick performance"

What do you like best?

The idea is fantastic - the goal of server-less deployment of code that means no hardware or OS maintenance and the practically unlimited scaling as a result.

What do you dislike?

Cost/performance ratio is not useful for our use case, which is a shame because on paper it should be a poster-child for Lambda.

Recommendations to others considering the product

Calculate the overall costs before going this direction.

What business problems are you solving with the product? What benefits have you realized?

We experimented with converting JPEG2000 files using the bundled GraphicsMagick library in the Node.JS flavour of Lambda. The converted file is then used to create smaller derivative image files - i.e. thumbnails. What we found is that the performance of converting a JPEG2000 file to a JPG was prohibitive in this framework. A typical JP2 for cultural heritage use is around 1.5mb and might be something like a 6000x4000 image. It was taking anything up to 13 seconds for a Lambda function to run, with the JPG conversion happening first then promise-based callbacks to process the source file into thumbnails. Multiplying the costs up for 16 million images means that it is actually cheaper to run a set of EC2 instances versus the costs of Lambda compute time.

AWS Lambda review by Administrator in Program Development
Administrator in Program Development
Validated Reviewer
Verified Current User
Review Source

"Awesome opportunities!!"

What do you like best?

The easy scalability and the very low usage cost.

Integrating AWS gateway and aws kinesis pipeline it's a huge plus as well!

At first I thought that the execution time would be a problem, but since I've started working a little bit more intensive with it, it proves me that it was faster than I though.

What do you dislike?

There were a few negative sides, especially in features, but dailly they're updating the way lambda works and now it is becoming huge!

Actually, I had problems to implement sails-waterline model adapter, since lambda wasn't planned to become a framework hosting function.

Recommendations to others considering the product

Study every single AWS service before head to development so you can minimize the time that you spend coding and maximize your integration with other systems.

What business problems are you solving with the product? What benefits have you realized?

I'm dealing with email marketing, sending, managing and templating thousands of emails daily.

Using sails-waterline to manage our models at a vpc mongo inside aws.

AWS Lambda review by <span>Rostislav W.</span>
Rostislav W.
Validated Reviewer
Verified Current User
Review Source

"AWS Lambda is the easiest way to get your code runnig in the cloud"

What do you like best?

- easy deployment

- 3rd party tools (serverless framework, node-labda)

- nodejs support

- you pay only for the time of execution

- detailed logs

What do you dislike?

- older version of node js

- only python, nodejs and java support (you can still upload binaries for ex. golang)

- limitations in configuration (can't be configured like virtual server)

What business problems are you solving with the product? What benefits have you realized?

I was solving batch image resizing. I needed quite a powerful virtual machine to handle the batch "realtime". The problem was that the server was doing nothing most of the time it was running. Lambda can scale seamesly out of the box and I don't have to pay for sleeping server.

AWS Lambda review by <span>Glen G.</span>
Glen G.
Validated Reviewer
Review Source

"Servlerless technology is the best"

What do you like best?

The option to save on EC2 or server cost is the best we could have, of course there is a tech debt we need to consider but always spin up services faster is great

What do you dislike?

The requirements to have cloud watch as scheduler, now with functions is easy

Recommendations to others considering the product

Make more flexible on coding and scheduling

What business problems are you solving with the product? What benefits have you realized?

Easy and faster deployments of small application without the need of deploy new infrastructure, servers

AWS Lambda review by <span>Giacomo C.</span>
Giacomo C.
Validated Reviewer
Verified Current User
Review Source

"Review Lambda"

What do you like best?

Low price, his scalability and semplicity. Deploy a lambda function is very simple and is not painful like manage a EC2 instance.

What do you dislike?

Sometimes logs doesn't work and is not simple to handle larger application with a lot of library and common files.

Recommendations to others considering the product

Keep in mind that is very simple to go to the wrong direction with lambda. But there is a lot of talk and resource to help you with this game changer

What business problems are you solving with the product? What benefits have you realized?

Low low low price, much less than EC2. Lambda solves scalability problems in a web application.

AWS Lambda review by <span>Marcus H.</span>
Marcus H.
Validated Reviewer
Verified Current User
Review Source

"Smooth ride on a steep learning curve"

What do you like best?

The platform works flawlessly but the plethora of feature and configuration is vast. Knowing what to do where is a challenge.

I love the UI and easy to navigate administrative functions. Even though I might not know what I should do I always know where I am.

What do you dislike?

The feeling over being overwhelmed with options. When should I use all of these functions?

Recommendations to others considering the product

Use Claudia Js to get the easy route to the cloud.

What business problems are you solving with the product? What benefits have you realized?

Not having a server but rather just a bunch of functions.

AWS Lambda review by Administrator in Management Consulting
Administrator in Management Consulting
Validated Reviewer
Verified Current User
Review Source

"I love AWS Lambda"

What do you like best?

Lambda is a wonderful product, My favorite feature is the possibility of containerize each of my service with minimum effort, without worry about scalability and server maintenance. The pay per use model is excellent.

What do you dislike?

Sometimes I worry about the response time of my code after a few minutes of the last execution, i understand that AWS Lambda need to load a new instance of my container. But maybe if there were any service to keep my code warm, these would improve response times.

I would like the integration between AWS SQS and lambda.

What business problems are you solving with the product? What benefits have you realized?

I am solving any kinds of problems, image thumbnail, video thumbnail, REST API. Currently i try to deploy all my code with lambda function.

AWS Lambda review by <span>Vasily S.</span>
Vasily S.
Validated Reviewer
Verified Current User
Review Source

"We've built serverless backend on Lambda."

What do you like best?

Ease of use and no extra administration. Lambda is great as a product which fully implements the idea of serverless computing.

What do you dislike?

Some early stage bugs/undocumented behavior, nothing major.

Recommendations to others considering the product

Just give it a try with small prototype, it's really fast. We started this way and soon discovered that we can do all of our business logic on Lambda.

What business problems are you solving with the product? What benefits have you realized?

We've built a completely serverless backend using Lambda for our main product - language learning mobile app.

AWS Lambda review by <span>Ng Z.</span>
Ng Z.
Validated Reviewer
Review Source

"I love Lambda"

What do you like best?

No need to care about scalability and software updates. Highly recommend Lambda to anyone who is tired of over paying for unused resources. Easy to think of software in terms of individual API endpoints

What do you dislike?

1. Process for embedding software libraries is a bit difficult now. Updating multiple endpoints is hard

2. Break even point is 11%. Kind of expensive

Recommendations to others considering the product

Very easy to use. Highly recommend

What business problems are you solving with the product? What benefits have you realized?

I run a API SAAS product. Converting to Lambda now. Together with DynamoDB and Lambda, I hope to achieve a serverless architecture

AWS Lambda review by <span>Justin E.</span>
Justin E.
Validated Reviewer
Verified Current User
Review Source

"Loving AWS Lambda, keep adding features and support."

What do you like best?

I love the simplicity of the product, the idea is brilliant.

What do you dislike?

The development tooling needs some work, deployment needs work.

Also the node support is lagging behind, its only on v.12 where as we are 5.x.

Recommendations to others considering the product

Be prepared to shift your ops time from managing servers to improving deployment.

What business problems are you solving with the product? What benefits have you realized?

We are using it for our authentication system, it works well.

AWS Lambda review by <span>Krishna B.</span>
Krishna B.
Validated Reviewer
Verified Current User
Review Source

"server-less architecture"

What do you like best?

The concept of server-less architecture to build applications

What do you dislike?

Wish it was more integrated with API gateway

What business problems are you solving with the product? What benefits have you realized?

we use it as a check up/down bot to monitor our API and send text messages if there is an issue - one page of js code and zero servers.

AWS Lambda review by User in Marketing and Advertising
User in Marketing and Advertising
Validated Reviewer
Verified Current User
Review Source

"Serverless computing is the future"

What do you like best?

Extremely easy to deploy with serverless framework. Simple to set up integrations with other AWS services.

What do you dislike?

Needs wider language support. Wish there were official support for serverless.

What business problems are you solving with the product? What benefits have you realized?

Running applications reliably without paying for idle time on machines.

AWS Lambda review by User in Computer Networking
User in Computer Networking
Validated Reviewer
Review Source

"Most recommended for serverless applications"

What do you like best?

The best thing about lambda function is that it is expensive and serverless.

What do you dislike?

The execution time limit of 5 mins. What if I want to run a python code that might need more than that hard execution timeout, it won't let me. I will have to switch it to EC2 instance in such cases that will end up costing me fortune

What business problems are you solving with the product? What benefits have you realized?

Benifits: Serverless, inexpensive, secure

AWS Lambda review by Industry Analyst / Tech Writer in Financial Services
Industry Analyst / Tech Writer in Financial Services
Validated Reviewer
Verified Current User
Review Source

"Cutting edge, always changing"

What do you like best?

I think that it's so infinitely scalable for a great price

What do you dislike?

I dislike that its too cutting edge. It's always changing

Recommendations to others considering the product

Help contribute to the library to make it better!

What business problems are you solving with the product? What benefits have you realized?

Using Lambdas as a backend. It was cool to use with dynamoDB

AWS Lambda review by Administrator
Administrator
Validated Reviewer
Verified Current User
Review Source
Business partner of the vendor or vendor's competitor, not included in G2 Crowd scores.

"Using in some AWS infrastructure as a backend or as a replace for dedicated instances"

What do you like best?

Execute little parts of code in response to events or api calls.

What do you dislike?

The first time that a function it's executed it doesn't always take the same time.

What business problems are you solving with the product? What benefits have you realized?

Fast backend Development

Kate from G2 Crowd

Learning about AWS Lambda?

I can help.
* We monitor all AWS Lambda reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.