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
Google Cloud Platform
Score 8.2 out of 10
N/A
Google Cloud Platform is a suite of cloud computing services used to build apps or take advantage of cloud infrastructural services, achieve legacy infrastructure modernization, or manage enterprise data and analytic needs.
N/A
Pricing
AWS Lambda
Google Cloud Platform
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
No answers on this topic
Offerings
Pricing Offerings
AWS Lambda
Google Cloud Platform
Free Trial
No
No
Free/Freemium Version
No
No
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
Google Cloud Platform
Features
AWS Lambda
Google Cloud 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.
We used it to build a real-time analytics dashboard with BigQuery, and it worked very well, with super-fast processing and output to the dashboard, as well as no server management. However, when we tried using cloud functions for a live chat feature, the cold start delays failed and made it feel too slow for real-time use. So, it’s lacking for this.
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.
The UI is so confusing. The console is good, but it is like a maze. There are too many menus and settings, and things do not work as expected. It takes time to get friendly, and it is not friendly for new users.
Support experience: Sometimes, you get a great engineer, but other times, it's very difficult to talk with them as they are unable to respond as expected and solve issues late.
Region and zone are issues, as not all services are available in all regions, which is lacking when deploying something in the same region or zone.
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.
8 because the platform is super powerful and flexible. It scales well, and services like BigQuery and GKE are excellent. However, the learning is difficult. The UI can be a bit frustrating at first, and some things aren’t friendly, especially for newcomers. So it’s suitable for high-level services, but lacks a little UI, making it a little low.
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
Google Cloud Platform is release later than Amazon web service, I think that why Google Cloud Platform can learned and optimized the Dashboard and some features that make it easy to use and can be cheaper than amazon web service.
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.
