Google Cloud Functions & AWS Lambda
Google Cloud Functions & AWS Lambda
First of all, I have to admit that comparing an alpha release with a two-year-old stable product is not completely fair. That said, I believe that some of the functionalities already offered by Google Cloud Functions will make a substantial positive difference, especially from a development point of view.
Here is a quick recap of the main functionalities of both products:
Functionality | AWS Lambda | Cloud Functions |
---|---|---|
Scalability & availability | Automatic scaling (transparent) | Automatic scaling |
Max. # of functions | Unlimited functions | 1000 functions per project |
Concurrent executions | 1000 parallel executions per account per region (default safety throttle) | 400 parallel executions (per function, soft limit) |
Max. execution time | 300 seconds (5 minutes) | 540 seconds (9 minutes) |
Supported Languages | JavaScript, Java, C# and Python | Node js, Go, Python |
Dependencies | Deployment Packages | npm package.json |
Deployments | Only ZIP upload (to Lambda or S3) | ZIP upload, Cloud Storage, or Cloud Source Repositories |
Versioning | Versions and aliases | Cloud Source branch/tag |
Event-driven | Event Sources (S3, SNS, SES, DynamoDB, Kinesis, CloudWatch) | Cloud Pub/Sub or Cloud Storage Object Change Notifications |
HTTP(S) invocation | API Gateway | HTTP trigger |
Logging | CloudWatch Logs | Stackdriver Logging |
Monitoring | CloudWatch and X-Ray | Stackdriver Monitoring |
In-browser code editor | Only if you don’t have dependencies | Only with Cloud Source Repositories |
Granular IAM | IAM roles | IAM roles |
Pricing | 1M requests for free, then $0.20/1M invocations, plus $0.00001667/GB-sec | 1M requests for free, then $0.40/1M invocations, plus $0.00000231/GB-sec |
Comments
Post a Comment