GCP hits the nail on the head. (Sometimes)
Updated April 14, 2018
GCP hits the nail on the head. (Sometimes)
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Google App Engine
[It's being used for] Testing across various departments (Skunkworks. POCs, including Apigee API Gateway).
- Client SDK and examples for integrating with services (Datastore/Storage/Pub/Sub).
- Lightweight deployment code/config (lightweight YAML).
- Autoscale (configuration and runtime).
- Flexible runtimes.
- Missing scheduler as a service. Has static cron, but no fault-tolerant, dynamic scheduling as a service. Azure has this.
- Documentation. Documentation can be stale, to terse, cumbersome to navigate.
- Deploy time and CI. Azure has Git hooks and auto update built in. So from commit to live can be under one minute. GCP more manual, and closer to 5+ min for same.
- Save time
- Save resources
- Near effortless scaling
Azure - too Windows. Do not want IIS or Windows OS.
AWS - too much configuration for the tasks at hand.
Heroku - too simple and too expensive and lacking features.
Pythonanywhere - lacking features.
AWS - too much configuration for the tasks at hand.
Heroku - too simple and too expensive and lacking features.
Pythonanywhere - lacking features.