AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
Netlify Platform
Score 9.9 out of 10
N/A
Netlify is a platform for developers from the company of the same name in San Francisco, used to build performant and dynamic web sites, e-commerce stores and applications. By uniting an ecosystem of technologies, services and APIs into one workflow.
$19
per month per user
Pricing
AWS Lambda
Netlify Platform
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Starter
$0
Pro
$19
per month per user
Business
$99
per month per user
Enterprise
Custom Quote
Offerings
Pricing Offerings
AWS Lambda
Netlify Platform
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Lambda
Netlify Platform
Features
AWS Lambda
Netlify Platform
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
Netlify is a static website host, so it obviously wouldn't work for hosting dynamic websites built in PHP, such as WordPress or Drupal. It works very well with static sites with a git codebase on something like GitHub. It has automatic deployments, which include preview websites. It works very well with this workflow. There are solutions for allowing content authoring on static websites on Netlify, but I would probably reach for something like WordPress or Drupal for that.
I can connect Github/Gitlab repos or drag and drop code folders directly to host them onto the platform, and can customize build and publish details. It handles all granular details itself, so I don't have to worry about configuring everything like I would have to do on an IaaS like AWS
Netlify Platform has inbuilt scalability support - meaning automatic upgrading of servers to handle traffic, without us needing to do anything at all, again, unlike IaaS, where we'd have to manually configure scaling
It has a built in CDN, meaning static applications can be served blazing fast over the web without worrying about traffic or latency
Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
We interact with the CLI via our CI/CD pipeline. It was very straightforward to get set up, and their documentation is thorough. There are a ton of examples online of various setups. We needed to deploy a React SPA, so we required redirects, which was straightforward with Netlify.
Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
Netlify Platform is the first choice that we are using in this organization continuously and it's been a very promising platform to use. It also maintains the things very well. it also giving a very good updates. It is very easy to use and very easy to learn. overall it is good.
Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.
