<story><title>Why you should not use Google Cloud</title><url>https://medium.com/@serverpunch/why-you-should-not-use-google-cloud-75ea2aec00de</url></story><parent_chain><item><author>aleph-</author><text>So piggybacking on this, I have a similar story to tell. We had a nice young startup, infra entirely built out on Google Cloud. Nicely, resiliently built, good solid stuff. Because of a keyword monitor picked up by their auto-moderation bot our entire project was shut down immediately, wasn&amp;#x27;t able to bring it up for several hours, thank god we hadn&amp;#x27;t gone live yet as we were then told by support that because of the grey area of our tech, they couldn&amp;#x27;t guarantee this wouldn&amp;#x27;t keep happening. And in fact told us straight out that it would and we should move.&lt;p&gt;So maybe think about which hosting provider to go with, don&amp;#x27;t get me wrong I like their tech. But their moderation does need a more human element, to be frank all their products do. Simply ceding control to algorithmic judgement just won&amp;#x27;t work in the short term if ever at all.</text></item></parent_chain><comment><author>setquk</author><text>I’m starting to favour buying physical rack space again and running everything 2005 style with a light weight ansible layer. As long as your workload is predictable, the lock in, unpredictability, navigation through the maze of billing, weird rules and what-the-fuckism you have to deal with on a daily basis is merely trading one vendor specific hell for another. Your knowledge isn’t transferable between cloud vendors either so I’d rather have a hell I&amp;#x27;m totally in control of and of which the knowledge has some retention value and will move around vendors no problems. You can also span vendors then thus avoiding the whole all eggs in one basket problem.</text></comment>
<story><title>Why you should not use Google Cloud</title><url>https://medium.com/@serverpunch/why-you-should-not-use-google-cloud-75ea2aec00de</url></story><parent_chain><item><author>aleph-</author><text>So piggybacking on this, I have a similar story to tell. We had a nice young startup, infra entirely built out on Google Cloud. Nicely, resiliently built, good solid stuff. Because of a keyword monitor picked up by their auto-moderation bot our entire project was shut down immediately, wasn&amp;#x27;t able to bring it up for several hours, thank god we hadn&amp;#x27;t gone live yet as we were then told by support that because of the grey area of our tech, they couldn&amp;#x27;t guarantee this wouldn&amp;#x27;t keep happening. And in fact told us straight out that it would and we should move.&lt;p&gt;So maybe think about which hosting provider to go with, don&amp;#x27;t get me wrong I like their tech. But their moderation does need a more human element, to be frank all their products do. Simply ceding control to algorithmic judgement just won&amp;#x27;t work in the short term if ever at all.</text></item></parent_chain><comment><author>bitL</author><text>I can tell a similar story with Amazon MWS, where even if we had access to &amp;quot;human support&amp;quot;, it felt like talking to some bad ML, not understanding what we were saying. Ultimately that start up was disbanded, never violating any rule they had, but flagged because of a false positive, and we couldn&amp;#x27;t even prove we didn&amp;#x27;t violate anything because we didn&amp;#x27;t even go live yet. It felt Kafkaesque, punishing one of a myriad possible intents due to malfunctioning ML, with no recourse.&lt;p&gt;Maybe support just needed to satisfy their quota of kicked out companies for the month, who knows?</text></comment>