4 ms·

> Derek’s point about savings is about list price differences that result from total system performance (and not any sort of special discounting). Obviously th

> Derek’s point about savings is about list price differences that result from total system performance (and not any sort of special discounting). Obviously that's the thing you'd choose to highlight in a public Google-hosted presentation after a strategic partnership that is a bonanza in marketing for Google Cloud. It wouldn't work so well to tell a room full of engineers "We moved to Google cuz they gave us a fat discount, one you can't get because you're not Twitter!" The fact that you allocated a top level URL for it is embarrassing (https://cloud.google.com/twitter/ https://cloud.google.com/twitter/). Can you imagine if Amazon advertised https://aws.amazon.com/netflix/ https://aws.amazon.com/netflix/?

dustinmoris 8y ago
> The fact that you allocated a top level URL for it is embarrassing (https://cloud.google.com/twitter/ https://cloud.google.com/twitter/). Can you imagine if Amazon advertised https://aws.amazon.com/netflix/ https://aws.amazon.com/netflix/? It's a case study. Google didn't create a one-off URL for Twitter, but have the same URL pattern for all their public case studies: - https://cloud.google.com/chilean-healthcare/ https://cloud.google.com/chilean-healthcare/ - https://cloud.google.com/now-ims/ https://cloud.google.com/now-ims/ - etc. Amazon has absolutely the same, except that their URL is slightly different, but I didn't think that there is a URL police which determines which URLs are considered embarrassing for case studies and which not: https://aws.amazon.com/solutions/case-studies/netflix/ https://aws.amazon.com/solutions/case-studies/netflix/