Google Compute Engine vs Linode

Need advice about which tool to choose?Ask the StackShare community!

Google Compute Engine

+ 1

+ 1
Add tool

Google Compute Engine vs Linode: What are the differences?

What is 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.

What is Linode? Deploy and Manage Linux Virtual Servers in the Linode Cloud. Get a server running in minutes with your choice of Linux distro, resources, and node location.

Google Compute Engine and Linode can be categorized as "Cloud Hosting" tools.

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, Linode provides the following key features:

  • Deploy multiple Linux distributions
  • Create Configuration Profiles which associate disk images and device nodes
  • Boot between configuration profiles

"Backed by google", "Easy to scale" and "High-performance virtual machines" are the key factors why developers consider Google Compute Engine; whereas "Extremely reliable", "Good value" and "Easy to configure" are the primary reasons why Linode is favored.

Snapchat, Harvest, and imgix are some of the popular companies that use Google Compute Engine, whereas Linode is used by eTobb, Infoshare, and GigSalad, LLC. Google Compute Engine has a broader approval, being mentioned in 587 company stacks & 414 developers stacks; compared to Linode, which is listed in 129 company stacks and 38 developer stacks.

Decisions about Google Compute Engine and Linode

Albeit restricted to only a few places worlwide compared to its peers in the cloud segment, I am yet to find another provider capable of delivering a score over 5000 (Geekbench) in a benchmark on a single CPU machine, and each machine costs $6 a month. For homelab and experienced users who don't need DBaaS or IaaC's, it's a pretty straightforward choice. A more comprehensive review of Vultr's HF machines can be found here.

See more

Chose Hetnzer over DigitalOcean and Linode because Hetzner provides much cheaper VPS with much better specs. DigitalOcean might seems like a good choice at first because of how popular it is. But in reality, if all you need is a simple VPS, you won't benefit much from the their oversubscribed datacenters which often underperform other competitors. Linode is also a good choice. They have cheaper options and performs slightly better than DigitalOcean. In the end, choosing a more affordable host helps you save money. That's important when you're running a tight ship.

See more
Stephen Fox
Artificial Intelligence Fellow · | 2 upvotes · 138.9K views

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More