Re:Twitter migrates data to Google Cloud
by sandGorgon on Wednesday January 23, 2019 @08:23AM
(#18977860)
it depends on usecases - i run a data heavy usecase. We deploy using docker swarm, so our redeployment is fairly well taken care of.
in terms of benchmarking - this is not something we care about (since we dont have so much CPU utilization), so probably its easier for me.
For my usecase, AWS has better administrative tools than google. I use Route 53, SES, S3 - in all those three, no other products come close (transfer acceleration...im looking at you).
The one place that I agree with you is Dataproc. That's far superior to EMR in terms of spin-up/down.
For us: on AWS/Azure we had to benchmark each instance when it came up and if it performed poorly it had to be reaped and redeployed constantly. The increased overhead in dealing with things "the AWS way" was enough by itself to offset the pricing difference with the steep AWS discount we were getting.
Understanding administrative overhead is complicated but I'm sure you are taking into account the cost of humans. (or, you've already absorbed the cost of automating it?) :)
As with all things; use what works for you. I'm just very happy with GCP over the others coming from bare metal.