How to Think About GCP vs Packet
What’s not to love about Google? They obviously know all about infrastructure...you know, inventing Kubernetes and such!
When it comes to cloud, comparing Packet with Google comes down to multi-tenancy vs single-tenancy. In short, if you want to run your own infrastructure the way Google does for itself, you’ll want to run on bare metal servers that are available globally. You’ll also want to inject a fair amount of opinion into what kind of hardware you use, and how your network is setup.
Unfortunately you can’t run the way Google does on top of GCP. Like AWS and Microsoft, GCP offerings primarily rely on virtualization and/or multi-tenancy to make things like their managed Kubernetes or other offerings possible.
|Native IPv6 Support|
|Cloud-init / Metadata Support|
|Spot Market Feature|
|Simple, Clean API|
|Deploys in Minutes|
|Extensive DevOps Integrations|
|Full Hardware Access||No|
|Private Deployment Option||No|
|Local & Global BGP||No|
|BYO IP Space||No|