5 ms·
The centralization of all major cloud engineering workforce in one city is ridiculous. With all the talk about distributed systems and fault-tolerance, etc., t
by polskibus 9y ago
The centralization of all major cloud engineering workforce in one city is ridiculous. With all the talk about distributed systems and fault-tolerance, etc., they are making Seattle pretty much a single point of failure for their cloud operations.
- nemothekid 9y agoBlame Amazon for that. It seems like to me, all the people with major cloud ops experience from building AWS are all now based in Seattle. If you want to poach that talent, you either have to convince them to move to Seattle, or open an office in Seattle. Companies opt to move to Seattle, which compounds the problem.
- mehrdada 9y agoPlease note that Google HQ is in Mountain View, CA, so expanding in Seattle is analogous to adding spare nodes in your distributed system, not single point of failure.
- polskibus 9y agoGoogle exec quoted in the article said that Seattle ‘is going to be basically Google Cloud’. It means that most of the engineering behind Google Cloud (not Google itself) will be there, implying the concentration I mentioned.
- mehrdada 9y agoI believe the logical implication of that sentence is backwards: it means most of the building will be used for Google Cloud as opposed to other Google products; it gives no information about how Google Cloud is distributed across Google offices, i.e. that building might be 100% GCloud but a minority of overall GCloud engineering.