AWS Lambda

AWS Lambda

4.5
(498)

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.

AWS Lambda Reviews

Ask AWS Lambda a Question
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • Industry
Ratings
Company Size
User Role
Industry
Showing 498 AWS Lambda reviews
LinkedIn Connections
Sign in to G2 to see what your connections have to say about AWS Lambda
Jonathan P.
Validated Reviewer
Verified Current User
Review Source
content

"Lambda is simple, cost effective and powerful."

What do you like best?

Lambda was beyond simple to setup. Using it in conjunction with AWS API Gateway and RDS services is actually simple to setup and leaves endless possibilities. Lambda connects directly with the Gateway allowing for quick connection between the two services and Lambda handles the rest from there.

What do you dislike?

The management interface can be a little quirky from time to time, however it's nothing that is not easily handled.

Recommendations to others considering the product:

If you have any need for serverless processing, Lambda is without a doubt the direction I would recommend. Coupled with the rest of the AWS platform, the possibilities for APIs and other services is nearly endless.

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

Using Lambda in conjunction with AWS API Gateway and RDS we are in the process of building our own API. So no matter what platform we end up on, all we have to do is write a new connection for that platform and our back end will always remain the same.

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

Thanks for letting us know!
Jay M.
Validated Reviewer
Verified Current User
Review Source
content

"Reliable and much useful tool. "

What do you like best?

Can configure any application by using lambda functions which easy to imitate and can be used from anywhere.It is much scalable tool used so far and best is that you don't have to manage servers. Apart from all these I like that I can easily integrate my node.js code into it and get it deployed in seconds

What do you dislike?

Sometimes when you are learning this tool then it becomes complicated due to some UI. But I think when you get used to it then it is very great tool. I also think that pricing is a bit expensive compared to google.

Recommendations to others considering the product:

My recommendation when you are considering for cloud services is that you should opt for aws cloud services rather then any other because it is easy to use once you get used to it and is also vastly used amongst developer communities so you can get a much help from there, Also aws provides best support whenever you are stuck in any kind of problem and it has almost all services for everything. AWS is so huge as you all know. You can definitely go for AWS Lambda it is very great product to use just look for pricing as google also gives good support and if using it in small poc then you can choose any one of them without looking.

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

I personally use AWS lambda for developing and managing our application over cloud platform. Whenever I get my hands on Alexa Skill then Lambda is a great tool to use. Apart from that we can use lambda for much greater purposes.

Sunil C.
Validated Reviewer
Verified Current User
Review Source
content

"Easy and scalable without need to manage servers"

What do you like best?

Can implement any application by directly using lambda functions which are very easy to imitate and can be called from anywhere.It is scalable obviously but the pro about it is that it is automatically scalable and best part comes when you dont have to manage servers.Apart from all these I like that I can easily integrate my python code into it and get it deployed in seconds.

What do you dislike?

I think the price is little more but its worth it.

Recommendations to others considering the product:

My recommednation to others considering cloud services is that you should opt for aws cloud services rather then any other because it is easy to use and is also vastly used amongst developer communities so you can get a vast support from there,Also aws provides best support whenever you are stuck and it has almost all services for everything,like aws lambda can be used for computing without managing servers so it is a cool thing to use.

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

I am using all the aws services for my cloud deployment requirements because aws is cool and easy to operate and apart from these it has vast functionality.I use aws lambda for deploying applications without need to manage servers.It is scalable so I don't have to think about any extra load.So I use aws lambda.

Pramod P.
Validated Reviewer
Verified Current User
Review Source
content

"Perfect for Serverless Computing"

What do you like best?

- Support of many languages like Node.js, Java, C#, etc

- Pay As You use, pay for invocation / usage time

- No need to keep your servers up all the time

- No worry of scaling & load balancing

- Nice integration with other AWS Services like API Gateway, AWS IoT, etc

- Best option for Microservice & Serverless architecture

- Very Cost effective solution

- Best & easy option for Alexa Skill Development

What do you dislike?

- Debugging becomes bit difficult sometimes

- Not able to use online editor in AWS Dashboard if source code contains many files

- Should provide dependency installation automatically (i.e. Dependencies mentioned in package.json of Node project should be installed automatically)

Recommendations to others considering the product:

Perfect for Serverless architecture

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

- Many tasks which does not require servers to be running 24x7

- Deployment of Alexa Skill Backend

Ronak P.
Validated Reviewer
Verified Current User
Review Source
content

"Reliable and widely used service !!"

What do you like best?

as a senior software developer i have been using AWS Lambda since 2014 and i highly recommend it for a rapid software development in industry very easily , the most wonderful thing about aws Lambda is that it is highly automated service platform in which user can do it's work very easily and interactively , so mainly it improves the performance of your application deployed over the cloud platform , it provides the dynamicity to your application which is handling a real time data to display and process in the back - end , it automatically manages the os updates for your instances , it also provides scale ability to your infrastructure , and it also monitors the total AWS infrastructure for availability automatically and smoothly , so in nut shell by using AWS Lambda you just need to focus on developing applications not on managing the infrastructure etc !.

What do you dislike?

As if now there is nothing to dislike about AWS Lambda !!

Recommendations to others considering the product:

As i described earlier it's highly scale able and frequently used tool for rapid real time application development ! 1

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

we use AWS lambda for developing and managing our application over cloud platform ! !

Shyamal S.
Validated Reviewer
Verified Current User
Review Source
content

"Run a service without managing servers"

What do you like best?

AWS Lambda is a compute engine that allows you to run and execute your computation code without need of maintaining servers.It has many best features like auto scalability which is require when using cloud as compute engine because as your users increase your code must work similiarly and handle those easily so AWS lambda is easily scalable.One another great thing is that it runs only when request is called i.e. you don't have to pay when your code is not running which reduces your useless cost by much.There are many other facilities provided by lambda which I have used till now.It is a great compute engine from my point of view.

What do you dislike?

I like everything about aws lambda,nothing to dislike.

Recommendations to others considering the product:

When you develop a webapp or web service which requires the code to be run on server side and also many times code takes much time to run on client's machine due to lack of hardware so at that times you can run the code on cloud and return results to the client's machine.So for running code on cloud side you require a better compute engine that scales automatically,is easy to use and costs less so aws lambda is fulfilling all those requirements and also is not that heavy on budget so I recommend using aws lambda for computation requirements.

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

I provide cloud related solutions to my clients and develop web app and services on cloud for my clients.I use aws cloud architecture for developing such services.So whenever I have to provide any computation related work for that particular app than I use aws lambda because it is easy to use and scalable and also costs less.

Sachin P.
Validated Reviewer
Verified Current User
Review Source
content

"Easy integration, language support"

What do you like best?

For minimum requirement or simple API, it is the best thing to start with. Easy testing up with inbuilt functionality to test lambda function with custom input types. Major development language support like Python, nodes.js etc.

It has various and all major trigger type available in AWS service e.g S3 and many more.

The best cost-effective lambda function in the market.

Sometimes the trigger on s3 fails to invokes, particularly transcribe job.

What do you dislike?

Dependencies and package management is a somewhat irritating process.

The first thing it requires custom python packages which are particularly compatible AWS Linux environment. Struggled a lot in the initial stage. Once created I think it should have remembered the dependencies.

Also, need to upload the whole package + code if the size is bigger need to upload via s3 bucket.

If the size increases the editor does not load up the code, so the development and testing cycle time increase with given into consideration that it needs to follow the whole process for uploading the package.

For the beginner, I guess the development support for video tutorial & detailed documentation could have been better.

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

For a quick small development process rather than creating a deployed web app service we do create Lambda functions. Mostly triggering a process on the event which re majorly AWS service like comprehend, transcribing etc. Also for data manipulation on this service as per our need is done.

Given the fact that it's serverless and reliable the real-time tailored output enabled.

Alok P.
Validated Reviewer
Review Source
content

"Very reliable serverless architecture implementation"

What do you like best?

The fact that it delivers on its promise. Lambda allows you to run code without worrying about servers. This reduces a lot of headache which comes with traditional architecture implementation. One thing that really blows my mind is how AWS Lambda scales up or down the internal servers being used depending on the needs of the function. Lambda, thus, speeds up development. Also, it integrates very well with other AWS services - S3, SNS, CloudWatch(indirectly) and pretty much any other service as you can always use the AWS SDK in your function.

What do you dislike?

One thing that I would expect Lambda to do better would be to provide a better UI and a better IDE to code. Having said that, one cannot expect all features as in a full-blown IDE like IntelliJ Idea. Another downside to Lambda is that estimation and planning for costs becomes very difficult. Also,

Recommendations to others considering the product:

If you are heavily invested in the AWS ecosystem, but have still not given Lambda a shot, you are missing out on a lot of powerful stuff. Since Lambda integrates fabulously with events that come from different AWS services, there is a lot that you can do using AWS Lambda. Lambda is best suited for cases where you can break down your functionality into smaller discrete functions. If that is not possible, it would be better to go with traditional backend.

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

We use several CloudWatch alarms based on custom metrics which send message to an SNS topic, which in turn invokes a Lambda function. We also use it to take manual snapshots in RDS, and also to delete those that are more than 1 month old. Apart from that, there are several other usecases that we use Lambda for.

John B.
Validated Reviewer
Verified Current User
Review Source
content

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

Gaurav B.
Validated Reviewer
Verified Current User
Review Source
content

"Best Cloud Platform for alexa "

What do you like best?

It is very simple and user friendly for startup and setup. We can use lamda for any cloud appllication. I hvae used with amazon alexa for testing purpose. I like best they provide millions hits per month on skill.We can use it for creating alexa skills.

What do you dislike?

Sometimes slow on slow speed networks.

Price is more but if you are student then basic plan works for one year.

Recommendations to others considering the product:

Anyone who wants to learn AWS lambda Do this documentation and proper working of it.

You can learn it from their documentation or you can go through video tutorials for learning.

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

I am creating alexa skills for development and studying more related to this. I have created sample skills for testing alexa echo dot device.

Rohan S.
Validated Reviewer
Verified Current User
Review Source
content

"Cheap and affordable for small code hosting"

What do you like best?

The best feature is auto scalability for the functions that we want to deploy. Serverless architecture so it will always run and we dont have to worry where and how it is going to run. AWS takes care of all the lambdas execution.

What do you dislike?

Multiple language support is not there together right now.

Recommendations to others considering the product:

Please use it... it will be good for you

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

The middleware programs, used for hiding several APIs or for providing a filter, we use AWS Lambdas for any application basically. We get a unique URL from amazon for each of the lambda which we can use in our application for any type of processing we we want. Also, we have to pay only for the number of seconds it is executing and not more than that. So it is very affordable that way

Hoshiyar S.
Validated Reviewer
Review Source
content

"Serverless architecture, easy to deployment and highly scalable"

What do you like best?

Its an easy to use and we are able to implement this without any server - just need to use the Lambda functions and it works very well. Deployment is very smooth as well as entry level developer can handle this task. Latency and data parsing is awesome. Log processing is very efficient. In AWS debugging task is very easy.

Its highly scalable for its services. Services charges are reasonable and we can easily scale the tooling services.

Overall great communication between webPortal and Lambda. Service availabilty is very nice.

What do you dislike?

Not much to dislike only one thing noticed thst cold state's first execution takes a bit more time but subsequent calls run very efficiently.

Recommendations to others considering the product:

Yes, i recommend for this. AWS - Lambda: Great serverless architecture, affordable cost and efficient services. Go for it.

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

With the help of AWS Lambda handled the unpredicatble load in very efficient way. Monitored the crtical issues timely and in easy way. As It works on demand basis so we are not worry about usage charge. Maintenance cost is zero as this done by vendor at their end.

Upgraded our existing architecture with latest technolgy (cloud infrastrucure) trend.

Rich W.
Validated Reviewer
Verified Current User
Review Source
content

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

A
Administrator
Validated Reviewer
Verified Current User
Review Source
content

"Serverless Power for Fast Paced Development"

What do you like best?

The power and flexibility to utilize lambdas to do pretty much anything you need. We use it for a few different startup firms we support for business critical and non critical systems. It is imperative that our systems are not only cost effective but fast to get implemented and easy to modify if needed. This was the huge win in our book on why we went with AWS Lambda as a solution for many projects even though other options might be more cost effective it always ended up on top and surpassing competitors in the serverless space. Our main implementation of ETL work was in need of cost optimizing and flexibility for new systems.

What do you dislike?

There are some compatibility issues when deploying to lambda with certain python libraries and environments but there are other services out there that help simplify that (so drawback that that may be necessary)

Recommendations to others considering the product:

Look at solutions generated by others for your situation using lambda as the community is huge and odds are there is something already created that you can use to kickstart your development.

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

Work with small but frequently changing ETL processes that we have been able to utilize lambdas to run vs keeping an ec2 instance constantly running.

Aaron H.
Validated Reviewer
Review Source
content
Business partner of the vendor or vendor's competitor, not included in G2 scores.

"SynerComm Serverless Solutions"

What do you like best?

The enviroment and the flexibility the serverless controlls allow me to deploy the code. The way it only runs when need is great from a managed service model where customers are only charged withwhat they use and then a partner can roll that into a payment plan for thier service.

What do you dislike?

Until recently the lack of some languagaes for our developers specifically the ones who would like to code in unsupported or obscure langauges. THe other issue I was having is understanding the security concerning and around the platform . Howevere by attending AWS i have now learned the controls to be able to put in place.

Recommendations to others considering the product:

THe now native powershell support has been great for the windows admins who have learned that language

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

We are currently running a demo for our clients in the cloud with a managed service to allow customers to access IP based listen to be consumed by their security endpoints in a native function. We are currently using this service for AWS and Azure whitelisting but will be expanding it as we test. This product then is managed by our team and connected to our customers provinding realtime protection and analysis of certain IPs and will eventually be applied to dynamic firewall and security controls. Once fully deployed we expect the portability of the code and scalability of the AWS environment to far outstrip our current capacity in our local datacenters.

Matthew P.
Validated Reviewer
Review Source
content

"AWS lambda makes our cost savings grow"

What do you like best?

I enjoy the massive boost our savings has occurred over the course of using this technology. We have setup large implementations between our Elastic Beanstalk Applications and our usability. Using Lambda, we are able to not only scale out our applications, but we can do so while knowing we can also lower costs and scale down when our metrics hit certain thresholds.

What do you dislike?

I do dislike the limited runtimes that are available in lamda, and the pre-written code for management. It does leave some desires for more customizable runtime environments which would give us much more control over what small applications we can use.

Recommendations to others considering the product:

I think our overall recommendation for others is that lambda makes small applications very easy to deploy in a serverless fashion. Lambda is the quickest way to experience serverless applications, and by using lambda you are on the right track to smaller apploications and easier management.

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

When I first started at the company, we had large dev environments that were never being used just accuring costs. We worked to make a large layered application in lambda to track usage and also alert us based on utilization and take appropriate action where needed. It is now a central piece to our environment standup.

julien T.
Validated Reviewer
Review Source
content
Business partner of the vendor or vendor's competitor, not included in G2 scores.

"Data transformation ETL in a minute"

What do you like best?

the serveless side fo the lambda, the fact that it super easy to instantiate, to use, you can use different languages such as Java, Pythonm and or javascript. I like also the fact that the cost of the lamba is almost nothing and it is a key component for Serveless architecture

What do you dislike?

the usage of lambdas as step functions, the limitation when transforming large files e g greater that 1.% Gb. Sometimes you could have issues and you don't know why you have an issue on which lambda function. the debugging logs of lambdas could be limited

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

we use the lambdas as an kinf of ETL because we have a lot of different Data sources and we need to clean them and transform them into a more canonical format. the buisness we do address is in the utility sector, and we are cllecting a lot of data from the field

Jemish R.
Validated Reviewer
Review Source
content
Business partner of the vendor or vendor's competitor, not included in G2 scores.

"AWS Lambda Review"

What do you like best?

Lambda is small server-less function that we can use in any projects which needs to be hosted or needs server.

It is very lightweight and very easy to configure. Just need to ARN key to configure.

What do you dislike?

I do not have major problem with AWS Lambda but you need to have a new tab for watching logs for debugging.

Recommendations to others considering the product:

If you do not want to use whole EC2 instances in Small type of projects or Just small services. You can opt for Lambda service for that. You can have very good support from the Community if you get stuck anywhere. You can just easily debug and run your projects.

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

I have been developing Nodejs Services for project. I have also developed small services that i deployed on Lambda and it is working very well.

jack j.
Validated Reviewer
Review Source
content

"Application building, responsive, supports multiple programming languages, economical"

What do you like best?

Amazon web services lambda is used to develop on demand applications that are very responsive to events and new information. It is quite economical as well. AWS targets starting a lambda instance within milliseconds. The developed applications are highly responsive and timely. It also supports multiple languages.

What do you dislike?

Although lambda supports multiple languages, it sometimes run slower with some programming languages. It also does not provide any control over environment to the users. It has extremely complex call patterns.

Recommendations to others considering the product:

Users who are looking for simple options to develop various easy and simple applications may consider using AWS lambda. It is highly efficient with reduced cost of execution and automatically manages computing resources required by the program running in the backend.

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

It is computing service that runs code in response to events and automatically manages the computing resources required by the code.

Aad M.
Validated Reviewer
Review Source
content

"Lambda, lambda, lambda"

What do you like best?

The no ops part. I’ve been managing systems in a datacenter for years and too much time is spent on lifecycle management, datacenter cost and server issues. With lambda we can run workloads whenever they need to run at incredibly low costs. We’ve been running some apps using lambda for 3 years and never experienced any issues with it.

What do you dislike?

When you run lambda inside of a subnet within a vpc, the performance decreases significantly. You need to keep the lambda’s warm for optimal performance but this beats the purpose of running it when it’s needed to run.

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

Mostly rearchitecting systems that contain lots of functionality that we had running as a single app. Decoupling all functionalities and building lambda functions to support each of these functionalities has greatly decreases the cost (84%), and increased the agility and innovation of the teams building and running them.

Dylan C.
Validated Reviewer
Review Source
content

"niche tool for distributed solutions "

What do you like best?

It is a very nice serverless system which is (somewhat) highly customizable for whatever you need. It has various options to help you integrate with your system in terms of security and cross-system accessibility.

What do you dislike?

It is a very complicated tool to troubleshoot. Being such a small and distributed system there is very few tools to help you fix any networking or connectivity issues you have to your other aws or cloud resources. It doesn't return very specific error messages and tends to have a poor UI similar to other AWS services.

Recommendations to others considering the product:

Be sure to choose an implementation that is either simple or well documented, as if you don't you'll find yourself troubleshooting for days on one simple issue that no one has accounted for and is almost impossible to find in your infrastructure.

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

Solved some server automation problems that we were having. We wanted to trigger certain scaling events and certain storage transfer events and we managed to accomplish these through a Lambda function.

Jinesh S.
Validated Reviewer
Review Source
content

"It automates the task of managing resources!! "

What do you like best?

i have been working with AWS Lambda for 1-2 years and it's very reliable and efficient tool for performing event driven server less computing , previously we have to face so many hurdles while developing cloud based application we need to take care about so many configuration before uploading our code to servers but by using AWS lambada you just need to write the code and upload it to the Lambada and rest of the things it'll do it by it self and thus it provides us a server less environment for developing cloud based applications easily rapidly for any kind of business requirements ! !

What do you dislike?

The quality of services is not up to the mark and pricing is little bit higher comparitevly!!

Recommendations to others considering the product:

it's one of the best service provided by AWS for automating the task of managing server configuration , so now you can stop worrying about managing provisioning those servers , and as i said earlier that the only thing AWS Lambada requires to work is your code!!

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

we use AWS Lambada to automate the task of provisioning and managing servers for developing cloud based applications ! !

anuj m.
Validated Reviewer
Review Source
content

"serverless managed service aws lambda"

What do you like best?

It is the most beautiful service provided by amazon, its a server less managed service which run the code without without using ec2 instance and we only charged when we use this. We run our code when we required with the help of lambda and only charged for use only. It have high availability and real time interface which help us a lot. when upload our code we need to run and it triggers automatically. very good managed service of aws. very useful.

What do you dislike?

main disadvantage i can say it auto trigger as we set time in it, in some cases it increase load on our source from which it is trigger. In case of outage we will be affected by them till we stop them.

Recommendations to others considering the product:

Everyone should need to use lambda which is very good and managed service by amazon to run your code and you are only charged when it run.

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

Its solving our main business problems of running code when we required and we only charged when it run.

Karl R.
Validated Reviewer
Review Source
content

"The Swiss Army Knife of AWS"

What do you like best?

Flexibility. You give me a way to trigger a lambda function and I can move mountains (provided it takes less than 15 minutes). Well, with step functions in front of it, I can even take longer than 15 minutes. Writing in node.js lets us consume complex JSON data streams and files quickly and easily. My team is really excited about all the possible applications, especially those we haven't thought of yet.

What do you dislike?

Not much so far. The Cloud 9 enviroment we code in could use a few more features, but as far as the lambda functions themselves, we have yet to hit a wall we couldn't climb.

Recommendations to others considering the product:

Try it for a month. You'll be hooked for life.

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

Data ingestion for a Data Lake. Log monitorning and alerts. We have a cheap and easy way to provide data to our Data Lake.

U
User
Validated Reviewer
Verified Current User
Review Source
content

"Great step towards Serverless Architecture"

What do you like best?

Very easy to start creating serverless architecture functions to offload and scale an API/Stack/App. Failover and fail handling is great. Especially when paired with SNS and SQS. Great integrations with a lot of AWS other services.

What do you dislike?

Kind of hard to do CI/CD with lambda since you have to package the code elsewhere and deploy it with CloudFormation or Terraform. A bit more complex than some other methods.

Recommendations to others considering the product:

CodeDeploy is a good companion with AWS Lambda

SQS is a great way to catch Lambda failures

Cloudwatch Alarms to monitor invocations and concurrent invokes to watch for spikes in usage/cost

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

Scaling functions / api to be more redundant, parallel processing, multi threaded, breaking up monolithic legacy apps into microservices. Breaking down old servers into microservices with lambda was a great and smooth transition

Austin C.
Validated Reviewer
Verified Current User
Review Source
content

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

Gopika J.
Validated Reviewer
Review Source
content

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

Helen P.
Validated Reviewer
Review Source
content

"Reliable and efficient service"

What do you like best?

I like it AWS Lambda beacuse it allows us to execute segments of our computational code that don't require actual virtual machines hosted on compute engines. This allows save time and us to achieve very low costs for simple pieces of code that can be run quickly a large number of times.

What do you dislike?

The price is a little more expensive if we compare it with other services that provide execution services of the lambda function.

Recommendations to others considering the product:

I recommend AWS Lambda for those that need scalability without maintaining servers.

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

As I mentioned previously, AWS Lambda has allowed us to save time and achieve lower costs with much less work. In general, is a amazing tool to run segments of code that don't need to be run actively.

AI
Administrator in Internet
Validated Reviewer
Verified Current User
Review Source
content

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

Glenn J.
Validated Reviewer
Review Source
content

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

Mitesh P.
Validated Reviewer
Review Source
content

"Excellent option for Serverless Computing"

What do you like best?

- Supports code in many languages

- Can be integrated with many services of AWS like IoT, Alexa, Cloudwatch, Kinesis, DynamoDB, API Gateway etc

- Scalable & Manages service. No worry of scaling

- Pay per usage pricing

- No need to keep server running

What do you dislike?

- Not able to edit code inline if source code contains many folders

- Does not have option to select required CPU cores

- Dependency installation should be done automatically. e.g. In case of Node.js, dependencies should be installed automatically based on Package.json

Recommendations to others considering the product:

Best service to use for Serverless architecture & Good for cost saving

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

Able to migrate most of our Web API into Serverless architecture.

No worry of scaling & managing server.

Affordable Pay Per Use model

Kyle P.
Validated Reviewer
Review Source
content

"Great for quick, serverless functions"

What do you like best?

I like how many languages are supported. It is also really nice that Amazon Web Services listens to their customers and increase the amount of run time allowed for each function.

What do you dislike?

It would be nice if they increase the action time to over 15 minutes. Increasing allowed run times would allow our company to move more of our scripting off of our current infrastructure and use the serverless features available in Amazon Web Services.

Recommendations to others considering the product:

Don't be afraid to play around and test the product out. Use X-Ray to troubleshoot your code.

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

We have used it for numerous scripts that previously ran on a server. This has allowed us to run the scripts without the need of the underlying server maintenance.

UI
User in Information Technology and Services
Validated Reviewer
Verified Current User
Review Source
content

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

UI
User in Information Technology and Services
Validated Reviewer
Review Source
content

"Lambda is Original Serverless ||| Scalable and Reliable "

What do you like best?

For me when someone says, serverless lambda comes to my even though other big cloud providers do provide the solution.

Lambda is cheap, takes away the pain of provisioning servers, couple with amazon gateway takes care of making an API.

Lambda is scalable and can handle multiple requests at a single timestamp. Since Amazon takes care of that, no need to worry about that

Lambda offers a million hits a month for free, so if you are a startup or are experimenting, this can be really good

Pricing of lambda is by nearest milli-second which is really good and cheap

Lambda layers are a really good way to experimenting and re-using packages

What do you dislike?

I hate the size limit on the packages, it is 50 MB for zipped packages and 250 unzipped and if you are deploying some complex models, this limit is easily reached. I can't say how many times, I've to work on this issue.

Recommendations to others considering the product:

Please start with the free tier in the initial setting and then move beyond that.

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

I was trying to deploy a machine learning model for my previous company on Lambda. Traditionally, it would had been an EC2 instance with flask/ngnix but this saves a lot of trouble.

E
Executive Sponsor
Validated Reviewer
Review Source
content

"Super glue for the cloud"

What do you like best?

The product grows on you over time. You might start with a simple function to respond to an event happening in your account and slowly (or quickly) grow the various things you use Lambda for., ending up with full serverless lambda apps. It's easy to get started and it grows with you.

What do you dislike?

It at times feel like a challenge to setup the right minimal IAM policies but recently Amazon helped out a lot with various CLI tools and the new console.

Recommendations to others considering the product:

TAke a bit of time to see any one of the lambda optimisation talks or presentations. There are quite some easy to do best practices that will save you a lot of effort later.

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

glueing a lot of components together, using lambd to respond to events happening in the accounts.

Alexa skill development

Slack Chatbot in combination with Lex

Data Pipelines based on separate servecies, mainly focussing on S3.

A
Administrator
Validated Reviewer
Review Source
content

"Re-platforming legacy application`"

What do you like best?

We don't need to worry about managing servers and there is no SSH or patching to worry about. This has made the time to development to new app very quick. Also it has significantly reduced our compliance scope.

What do you dislike?

We have tried a number of different frameworks - HAPI, Serverless, Express, etc and ended up with Serverless framework and custom event resolvers. None of the frameworks integrate very well with API Gateway and require us to use a {proxy} resolver vs utilizing more of the API Gateway features. The 15min timeout has been somewhat of an issue. The other issue we have had is finding security and compliance resources that are familiar with the serverless approach and are able to audit and certify our environment.

Recommendations to others considering the product:

Do some proof of concepts with more than one function working together.

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

We are using to replatform a legacy application and are writing all our business functionality into separate microservices on lambda.

UR
User in Research
Validated Reviewer
Review Source
content

"Easy code execution"

What do you like best?

What I like best about lambda is the serverless aspect of having a piece of code execute reliably using triggers. The most common triggers I use are scheduled, which makes scheduked jobs needing processing a piece of cake. The way that lambda communicates with cloudwatch makes it an easy way to debug any issues and monitor behavior as well.

What do you dislike?

I don't dislike much about the service, but often times I do find myself writing lambdas with many dependencies, making it hard to use the inline editor. But this is often overpassed by using a cloudformation template pointing to my local code.

Recommendations to others considering the product:

Do not forget to set up permissions allowing to create log streams. Otherwise you wont be able to analyze the behavior of the lambda!

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

Right now mostly for log analytics and api gateway use cases .With the api gateway approach I have realized how easy it is to set up an entirely serverless API which is awesome.

Conor F.
Validated Reviewer
Review Source
content

"Automation and governance with AWS Lambda"

What do you like best?

Lambda is easy to utilise with well-known languages. Using common languages like Python makes serverless coding very easy to do. Within a few minutes it's possible to have an application up and running!

What do you dislike?

Figuring out the security between Lambda and other services can be tricky in some cases.

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

We use Lambda to manage automated snapshots of EBS volumes, and we use it to manage our Route 53 DNS records automatically (for example, create a subdomain when an EC2 instances is created, and remove the record when it's stopped). Outside of that, we use Lambda to push metrics to third party monitoring services so we can govern our systems effectively.

Duncan H.
Validated Reviewer
Review Source
content

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

A
Administrator
Validated Reviewer
Verified Current User
Review Source
content

"Simple Server-less Micro-Service Deployments"

What do you like best?

After deploying several server-less services, we are quite impressed by Lambda. The ability to quickly deploy functions, with no architecture, across several languages, with interoperability between other AWS components, at an extremely low cost is really cool.

What do you dislike?

High likelihood of vendor lock-in when you start to use APIs and interact with other services, the micro-service now relies on the AWS ecosystem and thus is hard to achieve platform agnosticism.

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

We use Lambda to automate simple processes as well as to run code in languages that aren't supported by our main stack.

Ronald C.
Validated Reviewer
Review Source
content

"Lots of fun, makes infrastructure automation a breeze"

What do you like best?

AWS SDK is well-documented and you have full access to everything in AWS. Anything you can do in the console can be automated via AWS Lambda. You can use the most popular languages to write Lambda functions and the Cloud9 integration makes it very easy to test and deploy your functions.

What do you dislike?

Importing external libraries/modules/packages is a hassle. Shouldn't be that hard for a way to upload external libraries directly to the AWS Lambda Cloud9 IDE.

Recommendations to others considering the product:

If you're using Python, the Boto 3 docs are your best friend.

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

Have used Lambda to automate backups, inventory, trigger CRUD operations to a database via a web app and IoT device.

Edward M. V.
Validated Reviewer
Review Source
content

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

Drake B.
Validated Reviewer
Verified Current User
Review Source
content

"Eases your workload."

What do you like best?

You only have to worry about your code. Amazon handles the rest.

What do you dislike?

I wish more programming languages were supported.

Recommendations to others considering the product:

For those who do not want the incovenience of managing their servers or the startup, it is a great product.

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

Using Lambda to create triggers for Redshift and our VPC

William W.
Validated Reviewer
Review Source
content

"AWS Lambda review"

What do you like best?

AWS Lambda is very easy to work with and the tools for Visual Studio really make it easy to get started.

What do you dislike?

The primary thing missing at this point is the ability to do live debugging via Visual Studio. The logs work pretty well but actual debugging support would be awesome.

Recommendations to others considering the product:

Definitely look into the tools for Visual Studio. I missed these at first and struggled for a while, but these made all the difference.

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

We are working on converting several very large processes that run with cron jobs and message queues on on-premise machines to AWS Lambda.

Martin C.
Validated Reviewer
Review Source
content

"Brilliant"

What do you like best?

The ease of use within the console. I develop in dot net and the aws sdk for dot net is one of the best things I've used, being able to deploy your Lambda from within the Visual Studio IDE has saved so much time.

What do you dislike?

There is no folder structure within the console, having the ability to folder Lambdas would make organising them easier and would tidy up the console display

Recommendations to others considering the product:

Do it!

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

We had ec2 instances running all the time for small tasks that happen sporadically, moving them to Lambda has saved a lot of money

benjamin a.
Validated Reviewer
Review Source
content

"Amazing Serverless Magic"

What do you like best?

The best thing about AWS Lambda is the serverless platform. I've used serverless in conjuction with lambda to deploy several services, bots, and awesome tools which are used by my teams.

What do you dislike?

I think I like Lambda a lot, I'm not sure if I dislike much beyond the interface, but AWS doesn't have good UIs

Recommendations to others considering the product:

I'd love unlimited lamda run times, but 15 minutes is sufficent for most tasks.

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

I'm in security, so what I do is build consumable tools for devops teams. Lambda is great, allows me to use what I need when I need it.

Murtaza K.
Validated Reviewer
Verified Current User
Review Source
content
Business partner of the vendor or vendor's competitor, not included in G2 scores.

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

Dave N.
Validated Reviewer
Verified Current User
Review Source
content

"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 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!

Mark B.
Validated Reviewer
Review Source
content

"Simple Serverless Compute"

What do you like best?

I like the flexibility to break large applications into small, manageable chunks. We also use Lambda for periodic, one-off or scheduled tasks. Great for jobs that don't require "always on" application code running on our EC2 fleet

What do you dislike?

There's not much to dislike.. Deployment is easy, and integration with other AWS services is full featured. I suppose if I had to pick asomething to nitpick, I would say it would be nice to independently manage compute vs memory allocation to a Lambda function

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

Managing and routing SQS messaging, scheduled housekeeping tasks, other random one-off tasks.

Learn more about AWS Lambda

AWS Lambda Videos

Kate from G2

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.