Item: Google Compute Engine
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

We use it for microservices that has burst processing demands - they require lots of processing power for very short periods of time, thus requiring powerful hardware that, for most of the time, goes on without use. We wanted a cloud solution to avoid the hardware and infrastructure inherent to that scenario.

Pros and Cons

Better interface than AWS
Service has been very reliable
Excellent security policy structure

Documentation could be improved
Sometimes is hard to estimate how much we are going to spend

Return on Investment

Helped us save on hardware and infrastructure on microservice with variable demand
For stable load applications it was deemed too expensive and we kept on traditional bare metal solutions

Alternatives Considered

AWS Auto Scaling, Heroku Platform and Proxmox VE

Heroku was only viable for a couple of projects and AWS is a lot more complicated to configure and understand than Google Compute Engine.

Key Insights

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?

I wasn't involved with the selection/purchase process

Did implementation of Google Compute Engine go as expected?

Yes

Would you buy Google Compute Engine again?

Yes

Other Software Used

AWS Auto Scaling, Proxmox VE, VMware vSphere

Likelihood to Recommend

I would say that it is very helpful for scenarios with iregular processing power requirements, as situations where the application have burst of usage, or that have demands that change during the year or between the seasons. On the other hand, applications that have a very stable load can easily become too expensive for cloud usage.

How Google Compute Engine helped us save money

Overall Satisfaction with Google Compute Engine