These cloud players need to reduce prices. AWS has not significantly reduced prices in a long time.
Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
531–540 of 856 posts
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#532If a company like Westfield decides to get out of the leasing business, it makes sure its anchor tenants know there is some continuity of lease for their locations, because the value inherent in the property is the lease stability of the anchor tenant.
I begin to wonder if cloud has a parallel here: Does Google actually need, for selfish reasons, to inform significant cloud tenants in GCP that continuity of their business is core, and will be factored into any business development, or retiral, or sale options?
Elastic Search comes to mind: If you build to a dependency on Elastic, in GCP, its comforting to know it works in AWS but they are not an entirely identical product. From a business continuity model, mostly the same. Different tokens, different backend underneat the ES componentry. Does it matter? Depends how critical Clous ES is to your business.
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#533Googler here. My opinions are my own; I have no non-public knowledge on this topic. I do not understand the hyperbole around this report. Nowhere does it say that Google plans to shutter GCP if it doesn't reach #1 by 2023. > said people with knowledge of the matter. As in, people who may not have even been at said meeting which took place nearly two years ago, under a different VP and now a different CEO, and saw som…
> So it's not about being #1, it's about being profitable. The problem Google has with the developer community is largely around the fact that Google has a long history of pulling the rug out from our feet. There have been 3 stories on HN in the past couple weeks alone about Google products which have either been dropped or changed significantly such that they are no longer viable for developers to use. Google has lo…
Googles reputation was pretty much the decisive factor when a couple of years ago we decided to move from Heroku to AWS instead of GCP. Besides a prettier web interface GCP didn't really had anything going for them in comparison for our use cases, so why take the chance of having a rug pulled even if that risk might be quite small.
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#534Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#535> Ultimately, the Google executives decided in the spring of 2018 that the cloud computing opportunity was simply too big to give up on. All of the anecdotes in this article are from early to mid 2018. So why is someone leaking these stores 18 months later?
Because it took a long time to finally reach someone who was willing to leak it (plus article preparation and editing time).
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#536Even prior to this supposed leak, it would be really difficult as a developer to build anything reliant on Google's technology stack. There is a huge number of killed projects; abandoned platforms; and projects like maps where low/ no fees have become prohibitively expensive. Building atop Google is betting the farm on a fickle master.
And no offense to the Google team, but they are just awful at UI. I cannot imagine using anything Google related to manage complex hosting scenarios.
Well Amazon isn't exactly the king of great UI either and I'm not in love with Azure's cloud services platform management tools. All of these platforms have an extremely dense set of options which tend to change fast which leads to a very tough UI challenge and rapid UI rot.
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#537Earlier quoted context omitted.
> Google is far from the world’s “third largest provider” You're being a bit disingenuous. Your own source states quite clearly that Google is in the 3rd spot and arguably, if you cherry-pick results, you can place it in 4th. By cherry-picked results I'm referring to posting 2018 results and ignoring how GCP's revenue doubled in the last 18 months, nearly matching Azure's revenue.
So let’s look at the raw marketshare. It’s 10% of AWS. Also revenue != profit. If it was profitable enough would management be complaining?
> So let’s look at the raw marketshare. It’s 10% of AWS.
Yes, AWS is 1st. What's your point? Azure is 2nd and GCP is currently 3rd and catching up with Azure. What does AWS has to do with whether GCP is 3rd or 4th?
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#538Earlier quoted context omitted.
Amazon have been on HN recently for poor customer service with respect to billing for cloud services: https://news.ycombinator.com/item?id=21694835 Google could potentially win by being the least bad not the best.
Poor customer service is not exclusive to Amazon, google directly shut the product down which cannot earn search scale revenue. If you see comments below being downvoted by google PR for examples. I believe all these large cloud companies be it amazon, google or Microsoft deploy army of PR people and campaigns to downvote or try to remove comments which are critical. Especially I have seen this on HN, earlier when I…
> Especially I have seen this on HN, earlier when I commented on Amazon
Just curious - how do you "see" this? What exactly are you seeing?
I am not really sure if you have some magical HN karma level to see any special activity here. If so, I would be curious what that is.
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#539Earlier quoted context omitted.
Most major decisions aren’t made by what is cheaper - it’s made by which is safer.
Making operations google’s problem is precisely what drives BigQuery, FaaS and Dataflow adoption. Its operationally safer when you dont need a hadoop team to maintain your data infrastructure. See Nytimes, Twitter and Spotify for examples. Now if you’re talking about future-safety there was an argument...until a few hours ago.
Again, you’re talking about what’s “operationally safer” not what’s “reputationally safer”. If AWS goes down, no one is going to question your decision - and you’re in the same boat as a lot of other people. If GCP goes down and everyone else is up, people are going to ask a million question.
Every company you named isn’t the same thing as just arguing to the powers that be - AWS is what Netflix uses. AWS has many more “referencable clients” that matter.
Re: Google Brass Set 2023 as Deadline to Beat Amazon, Microsoft in Cloud
#540Earlier quoted context omitted.
I don't doubt that Amazon.com runs on its own dedicated "installation" of AWS, but are you saying that it doesn't run on AWS at all? That doesn't jive with the infamous "API mandate" email that Bezos wrote that essentially kicked off AWS. Have I been misunderstanding that email all along?
If you think the API mandate necessitated or created AWS then yes, you misunderstand that memo. The API memo simply mandated a service-oriented architecture. That can run on any compute and indeed predates AWS by several years. The origins of AWS are entirely unrelated, Amazon simply realized it was good at operating infrastructure. This led to the conception of offering infrastructure as a service. The initial AWS s…
I'm confused because on the one hand you say that their needs are very different and then on the other hand you say that they are using AWS. Another commenter also pointed out that they are using AWS.
I think the only needs that are likely different are scale, so bigger instances, and the fact that they have a massive legacy infrastructure that can't be easily migrated off of. So that's pretty much what I would expect; Amazon.com does use AWS for new stuff but is still operating a lot of legacy as well.