4 ms·
This could be a good forcing function for them to get their act together on cloud. However, I've heard that teams internally can't build on google cloud for var
by polyomino 6y ago
This could be a good forcing function for them to get their act together on cloud. However, I've heard that teams internally can't build on google cloud for various reasons. It may even make more sense for them to directly spin off onto AWS. Even "seperate" companies like Waymo build their systems on the internal google infra.
- easton 6y agoI'd imagine (although I don't work there) that it has something to do with datacenter availability. Google probably has a lot more datacenters than are available in Google Cloud used purely for internal workloads that run on their commodity hardware, which was what Borg was designed to run on. It's much easier to manage internal workloads by saying "it has to work on this" instead of letting each individual team go wild on Google Cloud and spin up whatever they want, which is how you get into an unmanageable flustercluck of shadow IT. Coupled with "Google-scale"(tm), where every service has to be able to scale globally (which is why they have so many datacenters and boxes in ISPs, etc.), it'd be difficult to manage that real estate the same way as companies do on your cloud (what if you need to bring up a ton of Gmail or YouTube traffic and the datacenter is at 97% load because Google Cloud had a good sales month? Not an impossible problem to fix, I suppose, but you could suddenly find yourself without enough hardware when you're talking about Google sized traffic.) I suppose AWS figured it out, although I always figured amazon.com didn't exactly compete for resources with outsiders.