Overall Satisfaction with Google Compute Engine
Most development servers and build machines are migrating into Google Cloud Compute engine. This allows us to spin up/down resources on demand based on workload, product needs, etc. QA does the same for testing resources.
- Fast
- Great CLI
- Great APIs
- gcloud CLI is very broad
- Billing detail could get more finer grained
- We are promised lower total cost and some discounts are in place
- In practice, at first migration, the cost is just as high as any prior cloud
- However, with clever use of APIs we should get a positive ROI
- Amazon Elastic Compute Cloud (EC2) and Azure Kubernetes Service (AKS)
Similar in capabilities, slightly slicker APIs and CLIs. More observability in the default UI and the CLIs. Easier to setup, the google console is slick. Azure has a good user interface as well with lots of documentation to help. CLI is slightly less intuitive, but decent. AWS I find is the most lacking, most convoluted and complex.
Do you think Google Compute Engine delivers good value for the price?
Yes
Are you happy with Google Compute Engine's feature set?
Yes
Did Google Compute Engine live up to sales and marketing promises?
Yes
Did implementation of Google Compute Engine go as expected?
No
Would you buy Google Compute Engine again?
Yes
Google Compute Engine Feature Ratings
Using Google Compute Engine
Pros | Cons |
---|---|
Like to use Easy to use Well integrated Consistent Convenient | Requires technical support Slow to learn |
- CLI
- API
- Instance management
- Networking setup
- Orchestration
- Scheduled instance allocations