That was the first project which trained me not to use Google products. I remember reporting by a ton of stuff and then never hearing back and things never improving until much (multiple years?) later when I’d stopped using it. I was profoundly unsurprised when AWS ate their lunch.
Amen, amen, amen. This is so frustrating to me because in general I really like GCP as a platform, and I think they're doing great things with stuff like Cloud Run.
Case in point, I like Firebase a lot, and I think Firebase Auth (aka Google Identity Platform) is a great product. But it took them about 2.5 years between releasing their initial support for a second factor, which was originally SMS only, and allowing a TOTP (e.g. Google Authenticator/Auth) 2nd factor. And they still don't support "remember this device" functionality, so every time someone logs in they always need to enter the 2nd factor. I literally can't think of any major site (especially Google's own) that doesn't support "remember this device", and yet it just must be a detail that's not "important enough" to get someone at Google a promotion.
They did close my textbook example of that but it took half a decade to implement HTTP to HTTPS redirects, which basically every large customer wants to make compliance easier:
Here is my similar (though not as long) example - point-in-time-recovery on postgres: https://issuetracker.google.com/issues/78448400. Interestingly, it had the same problem with 0 communication from a Google PM until early 2020, so maybe they hired someone at that time who convinced them you can't treat business customers the same way you do consumers.
Sure it wasn't enough alone to outlet outplay AWS, but Google would have been worse off without it
GKE (with Autopilot) is firmly set in my "day 1 toolbox" if I were to start a new company, assuming K8S was the right tech choice.
As long as you don't rely on implementation details like a specific Ingress Controller that needs special annotations, this is exactly what Kubernetes does, and the reason why you have Helm Charts that don't need to take into consideration which the underlying cloud is.
Going back to what we had before, you had to be very aware of exactly which cloud provider you'd use. And since AWS had about 80+% of the market then, that meant that instructions for how to run things on Google's cloud were not very good, if they existed at all.
That was not the point of Kubernetes.
And if it was, it did not realize that point for many years.
The problem is that GCP for some reason just doesn't align with many corporate customer requirements (ie: support, stability, never kill anything, available resources, etc.) and an engineer friendly product (GKS) does nothing to alleviate that. It makes GCP better in an area it was already better in and doesn't at all fix the tangential reason companies actually avoid it (or rather from what I hear either migrate off of GCP eventually or use it as just a secondary cloud provider).
Google famously uses lots of custom versions of infrastructure software while the rest of the world uses something else. Obviously that has served then extremely well, but the rest of the world wants stuff they are familiar with. It really took Google years to fully grasp that.
Most of Google's problems in B2B reflect that the organization has little concept of customer service, in the sense of serving customers. It's not the technology.
The current problem with AI for Google is that the good stuff costs a bit too much to give away with search. That problem may be solved, or evaded. Most searches or questions don't need a large language model. I expect to see systems where you ask a question, and if it's hard, you get something like "That's a hard question. Give me a minute to work on that. Meanwhile, here's a word from our sponsor."
This, exactly. Google is fantastic at research, great at development. It's terrible at product. Or, specifically, all the bits of product that aren't R&D. MapReduce, Tensorflow and Kubernetes are all examples of technical successes that Google has spawned. None is a product. You can't buy them, buy support, or, you know, actually talk to someone if something goes wrong.
That's why Google cloud has failed so far. It's not the tech; big G can go toe to toe with Amazon and MS on that. It's that enterprises want contracts and support and relationship managers and all that stuff. That just doesn't seem to be in Google's DNA. Unless they can adress that, they're not going to win with big org customers.
They might win the startups - where the customers are themselves techies who are OK with self supporting, looking up Stackoverflow, asking ChatGPT, etc. But unless they can address the people angle, I don't see Vertex gaining meaningful traction against Amazon or OpenAI/MS.
Perhaps, but they seem to be in a better position than many to get that cost to a reasonable level.
They've got the scale, the research side, lots of experience with models of different sizes, they own TensorFlow, they produce and deploy their own Tensor chips (so I would guess are not dependent on Nvidia's tech at 10x markup), and have lots of experience in datacenter power efficiency.
This is all just based on what I've read in tech news. I happen to work at Google but don't have any insider info here. I'm biased, but they seem to be in a good place.
I agree with another commenter, where Google missed the boat was cloud. Ironically, AppEngine came out pretty early in 2008, but its original incarnation was much too "Google-specific". Google just didn't have the corporate DNA to understand that, sure, Datastore can allow infinite horizontal scalability, but most people don't want to deal with eventual consistency, and they just want a plain-old SQL DB. It took Google a long time to come around to understand how other businesses use their infrastructure.