4 comments

[ 3.3 ms ] story [ 20.6 ms ] thread
I don't understand this statement:

>Due to the way GCE instances are deployed (in containers) they do not suffer from noisy neighbour syndrome

I understand the second half of the statement might be true, but it doesn't follow from the first.

What are the big downsides of GCP to other options?
I'm not sure I would describe them as big downsides but AWS does have advantages in some areas.

RDS - Amazon's database service supports more database engines; MySQL, MariaDB, PostgreSQL, MSSQL and Oracle are all available. GCP has Cloud SQL but it only supports MySQL and PostgreSQL at the moment. I'm sure that will change. RDS also has some advantages around getting your data in from an external server.

AWS also has more services making it easier to get up and running quickly. Whether that's a good thing or not is down to personal preference. Those services tie you into AWS pretty heavily. That's fine providing you are comfortable with it. Google are more focused around open standards.

>Due to the way GCE instances are deployed (in containers)

I'm aware that G run their stuff in containers and its likely that the supporting systems for GCP ( console, api stuff ) runs in containers.

dmesg output on an instance i'm looking at now shows kvm as the hypervisor (which can be contained )

But what evidence is there to say instances are actually in containers ?