4 ms·

I've been a GCP consultant for close to a decade now. Google messed up big time lagging behind in AI - they just kept increasing prices in other products for ab

by neya 1y ago

I've been a GCP consultant for close to a decade now. Google messed up big time lagging behind in AI - they just kept increasing prices in other products for about 5 years straight (CDN, for example) and did nothing to productize AI. I'm of the belief that ChatGPT should've been their pilot project. What they have now (AI mode) in Google should've been there well before ChatGPT. But, all that aside, you know what they're really good at? Google Cloud. I'm a user of all the major Cloud providers and nothing beats GCP's interface. Azure? Complicated, buggy and unreliable. There's some exploit every quarter. AWS? Overly complex security policies even to deploy a basic app, very enterprise focused and startup-unfriendly. GCP - you can be up and running on a serverless/VM instance in your lunch break. Simple, reliable, scales effortlessly. We serve 10M+ visitors on there and we've had zero issues in the last half a decade with them. They suck at a lot of other things and they have a lot of other problems. But boy, are they good at Cloud. No wonder even Apple is their customer. It's one of the few products from Google where you can say "it just works".

jart 1y ago
I think App Engine was really ahead of its time in showing how simple cloud deployments can be. It had a similar ease of use as setting up a YouTube account. For that reason, a lot of people thought of it as a toy, which was kind of unfair because companies like Niantic were able to build global products on it. So a lot of Google Cloud afterward ended up being designed to be more "normal" like how Amazon is. Now people are seeing what normal gets them, so maybe it's going to be time for the Google way of doing things to finally shine. (Disclaimer: I'm a Google employee)
- mind-blight 1y ago
  Ah, that's a shame they went that way. What I tell people when they're first getting into GCP is that it's gonna be a passion to set up what you want. But, the offerings are great, and once it's working, it'll just work
- dekhn 1y ago
  App Engine caused a huge innovator's dilemma for Google when it came to cloud. It only addressed a set of use cases around web application development- Folks would ask "why shoudl we build a low-margin cloud?" and I'd tell people: "if I can't import numpy, App Engine is useless to me". Eventually, the useful bits of AE were extracted to other services with APIs (datastore is one example), but it wasn't until google built a full GCP that they started to see real cloud growth (revenue). "Normal" is what most of us want.
- keeda 1y ago
  App Engine was the OG serverless before "serverless" was even a term: https://trends.google.com/trends/explore?date=all&geo=US&q=serverless,google%20app%20engine&hl=en-US https://trends.google.com/trends/explore?date=all&geo=US&q=s...
  - spwa4 1y ago
    C and Perl CGI, and later PHP, would like a word ... (CGI is a webserver starting a binary in response to a web request, essentially piping the request into stdin and sending stdout back to the client, in some ways it's brilliantly simple and very unix-y)
    - keeda 1y ago
      Oh in terms of coding, definitely other simple options existed. But you still had to go through the work of provisioning a server, deploying your code to it, and then getting a public IP address and a domain name before you could access it. I meant in terms of going from "0 to Cloud", GAE was ahead of its time.
      - spwa4 1y ago
        Most ISPs let you host CGI and later PHP files on your account, to encourage people to make websites. A guestbook, for example. For a while this was really popular.
        keeda 1y ago
        Oooh, that's interesting, I was not aware of that!
- neya 1y ago
  I totally second this. AppEngine was way ahead of its time. I used it for all my projects back then. The only reason I stopped using it for clients because even internal Google employees had no idea when the plug might be pulled out on AppEngine. AppEngine supported Elixir far earlier than anyone else (Elixir is my main go-to stack)
JustExAWS 1y ago
I am also a cloud consultant focused on AWS and a former employee of AWS ProServe (I have no love lost for the company). But if you are a consultant, why pray tell are you spending that much time in the console except for occasional monitoring? Everything is either CLI commands or infrastructure as code. And the issue with Google in particular is their customer support and business enterprise go to market sucks. The sales guys at ProServe use to run circles around GCP and never really took them seriously or had talking points. For big contracts we mostly had to compete with Azure because big boring enterprise was already using Microsoft. When we did have to compete against GCP - and their sales team didn’t blow up the deal themselves - we just had to say “do you really want to trust Google with your workloads? Look at their history of abandoning products and raising prices” Apple is a customer of all of the big cloud providers and was on stage at last year’s reinvent. AWS throws money and people at startups. I’ve been on three sides - working at a 60 person startup who hosted on AWS, working at ProServe and now a third party consulting company where many deals come about because of AWS funding.

by neya 1y ago

jart 1y ago

I think App Engine was really ahead of its time in showing how simple cloud deployments can be. It had a similar ease of use as setting up a YouTube account. For that reason, a lot of people thought of it as a toy, which was kind of unfair because companies like Niantic were able to build global products on it. So a lot of Google Cloud afterward ended up being designed to be more "normal" like how Amazon is. Now people are seeing what normal gets them, so maybe it's going to be time for the Google way of doing things to finally shine. (Disclaimer: I'm a Google employee)

mind-blight 1y ago
Ah, that's a shame they went that way. What I tell people when they're first getting into GCP is that it's gonna be a passion to set up what you want. But, the offerings are great, and once it's working, it'll just work
dekhn 1y ago
App Engine caused a huge innovator's dilemma for Google when it came to cloud. It only addressed a set of use cases around web application development- Folks would ask "why shoudl we build a low-margin cloud?" and I'd tell people: "if I can't import numpy, App Engine is useless to me". Eventually, the useful bits of AE were extracted to other services with APIs (datastore is one example), but it wasn't until google built a full GCP that they started to see real cloud growth (revenue). "Normal" is what most of us want.
keeda 1y ago
App Engine was the OG serverless before "serverless" was even a term: https://trends.google.com/trends/explore?date=all&geo=US&q=serverless,google%20app%20engine&hl=en-US https://trends.google.com/trends/explore?date=all&geo=US&q=s...
- spwa4 1y ago
  C and Perl CGI, and later PHP, would like a word ... (CGI is a webserver starting a binary in response to a web request, essentially piping the request into stdin and sending stdout back to the client, in some ways it's brilliantly simple and very unix-y)
  - keeda 1y ago
    Oh in terms of coding, definitely other simple options existed. But you still had to go through the work of provisioning a server, deploying your code to it, and then getting a public IP address and a domain name before you could access it. I meant in terms of going from "0 to Cloud", GAE was ahead of its time.
    - spwa4 1y ago
      Most ISPs let you host CGI and later PHP files on your account, to encourage people to make websites. A guestbook, for example. For a while this was really popular.
      - keeda 1y ago
        Oooh, that's interesting, I was not aware of that!
neya 1y ago
I totally second this. AppEngine was way ahead of its time. I used it for all my projects back then. The only reason I stopped using it for clients because even internal Google employees had no idea when the plug might be pulled out on AppEngine. AppEngine supported Elixir far earlier than anyone else (Elixir is my main go-to stack)

JustExAWS 1y ago

I am also a cloud consultant focused on AWS and a former employee of AWS ProServe (I have no love lost for the company). But if you are a consultant, why pray tell are you spending that much time in the console except for occasional monitoring? Everything is either CLI commands or infrastructure as code. And the issue with Google in particular is their customer support and business enterprise go to market sucks. The sales guys at ProServe use to run circles around GCP and never really took them seriously or had talking points. For big contracts we mostly had to compete with Azure because big boring enterprise was already using Microsoft. When we did have to compete against GCP - and their sales team didn’t blow up the deal themselves - we just had to say “do you really want to trust Google with your workloads? Look at their history of abandoning products and raising prices” Apple is a customer of all of the big cloud providers and was on stage at last year’s reinvent. AWS throws money and people at startups. I’ve been on three sides - working at a 60 person startup who hosted on AWS, working at ProServe and now a third party consulting company where many deals come about because of AWS funding.