Need advice about which tool to choose?Ask the StackShare community!
Google Compute Engine vs Civo: What are the differences?
Google Compute Engine: Run large-scale workloads on virtual machines hosted on Google's infrastructure. Google Compute Engine is a service that provides virtual machines that run on Google infrastructure. Google Compute Engine offers scale, performance, and value that allows you to easily launch large compute clusters on Google's infrastructure. There are no upfront investments and you can run up to thousands of virtual CPUs on a system that has been designed from the ground up to be fast, and to offer strong consistency of performance; Civo: Built for speed and simplicity, with k3s under the hood. It is a community-driven cloud platform, with all the features a developer could need. If you want it, we'll build it – your vision shapes what we deliver.
Google Compute Engine and Civo belong to "Cloud Hosting" category of the tech stack.
Some of the features offered by Google Compute Engine are:
- High-performance virtual machines- Compute Engine’s Linux VMs are consistently performant, scalable, highly secure and reliable. Supported distros include Debian and CentOS. You can choose from micro-VMs to large instances.
- Powered by Google’s global network- Create large compute clusters that benefit from strong and consistent cross-machine bandwidth. Connect to machines in other data centers and to other Google services using Google’s private global fiber network.
- (Really) Pay for what you use- Google bills in minute-level increments (with a 10-minute minimum charge), so you don’t pay for unused computing time.
On the other hand, Civo provides the following key features:
- Developer focussed, developer led
- Fast, but powerful
- Management CLI
GCE is much more user friendly than EC2, though Amazon has come a very long way since the early days (pre-2010's). This can be seen in how easy it is to edit the storage attached to an instance in GCE: it's under the instance details and is edited inline. In AWS you have to click the instance > click the storage block device (new screen) > click the edit option (new modal) > resize the volume > confirm (new model) then wait a very long time. Google's is nearly instant.
- In both cases, the instance much be shut down.
There also the preference between "user burden-of-security" and automatic security: AWS goes for the former, GCE the latter.
Pros of Civo
Pros of Google Compute Engine
- Backed by google87
- Easy to scale79
- High-performance virtual machines75
- Performance57
- Fast and easy provisioning52
- Load balancing15
- Compliance and security12
- Kubernetes9
- GitHub Integration8
- Consistency7
- Free $300 credit (12 months)4
- One Click Setup Options3
- Good documentation3
- Great integration and product support2
- Escort2
- Ease of Use and GitHub support2
- Nice UI1
- Easy Snapshot and Backup feature1
- Integration with mobile notification services1
- Low cost1
- Support many OS1
- Very Reliable1