This is the entire problem. Swap “Google” for “AWS” in the article and you’d have legions of folks calling foul on the article. Instead, most folks are nodding along to the article going “yep, seems like something Google would do all right…”
Google’s problem remains its reputation for turning things off.
The issue is that folks here think GCP is the same thing as Google Reader. That's absurd.
Google is currently building a massive $500 million datacenter outside of Reno as we speak, and has 10+ billion invested in their datacenter cloud offering buildout this year alone.
GCP and the entire physical infrastructure isn't going to get "turned off" if it isn't #1 in the market in 3 years, that's just silly.
The issue for me isn't Reader itself but what it says about the disconnect between Google management and us, the users of Google products. That seems to have happened around the time Google went from _having_ a "user base" to being effectively ubiquitous. I can't speak for others, but Google of the 2000s "got" the hacker/nerd mindset in a way that was the closest thing to empathy I've ever felt from a corporation. That sounds naive to write down here in almost-2020, but that was how it felt at the time. When Reader died, so did that feeling, and now all of us are running around unsure if the Google products we personally care about are the ones Google management care about. Leaks like this one do not inspire confidence in that.
Free consumer products are not the same as paid enterprise services. The markets are entirely different, and ascribing the fate of Google Reader as a sign of anything on the B2B front doesn't make sense.
> Free consumer products are not the same as paid enterprise services.
They may have different revenue models, but there is little difference when it comes down to management killing services which aren't profitable.
If there is a difference, it is that Reader could be maintained at little cost, while GCE (when it gets the axe) could potentially be costing google hundreds of millions per year to keep running.
There have been plenty of other cases where google has burned bridges with the technical crowd which they should have embraced as champions for selling services. Killing off XMPP support was another prime one for me, and absolutely affected paid enterprise customers as well.
Reader could only be maintained at little cost if its dependencies were stable. But stable infra doesn't get you promoted, so every service needs to be staffed indefinitely (to keep it on the upgrade treadmill) or killed gracefully before prod explodes.
To be fair, the switch to mobile-first did more to kill XMPP than Google did. It's a lot better now a decade later with all the XEPs, but now there's nobody there to talk to so it's too late.
Just a cursory look at killedbygoogle.com will show you a list of products that fall in the category of not free and used by business (Hired by Google) and/or were products that developers integrated with their own software that was killed.
As a developer or a company, why should I trust Google as a platform?
It's not just Reader and all the other services. It's really crappy customer service too. Reddit's got a good thread going about someone that paid up on GSUITE that got their account locked. You have to hope a tweet goes viral to get help.
That's irrelevant. Its about trust, commitment and sticking it out. Google's penchant of throwing shit against a wall to see what sticks seems to prevent them from applying themselves to increase the stickiness of their shit.
You simply cannot trust Google to do right by me, the user. That's it.
See, the thing is though, that they kill stuff that DOES stick as well. There's plenty of stuff in the Google Graveyard that was still widely used, with large user base, and they kill it anyway. There's no consistent logic to their killing of products. Sometimes they simply don't want to update it, sometimes it's purely internal politics (G+), sometimes there's just no reason we can find.
What people believe about them matters, not whatever internal rationalizations may or may not have occurred.
Aside from their bad reputation for killing products, they also have a bad reputation for providing next to zero human support services for their products - even if you do pay for them.
AWS has launched a hundred small products which anyone can signup for on the spot, it’s not that different than consumer product releases. And it’s also not the opaque enterprise sales process of Oracle and IBM where things move at a way slower pace.
It’s somewhere in between and if Google started launching a bunch of new DB and other infrastructure products I’d be worried about adopting them individually - not worried that the entire data centres and business divisions getting shut down. Because Google will probably move on to another product without thought of the last one.
Agreed that Google isn’t going to announce one day that they’re going to demolish all the datacenters in 30 days, but that doesn’t mean that GCP has any guaranteed future either. If Google leadership decides to walk away from cloud hosting, it’ll come in the form of reallocated engineers, reduced headcount, smaller conferences, and a general transition to “maintenance mode”. (At which point it’s a corporate backwater and everyone who can transfer out will.)
But for companies picking a cloud platform tomorrow, that’s a fate as good as death! AWS and Azure won’t slow down development and new features, so a couple years after GCP stops being a priority, it’ll start also being a bad deal, and a couple years after that it’ll be a straight-up strategic liability. THAT is why anything other than full-throated support from Google leadership for indefinite GCP investment will lose them business.
And maybe they won’t kill it, but I ve had a number of times platform changes killed features I used. Thing is, with a company I pay for I can vote with my wallet. With Google it’s just sending a message and hoping it doesn’t end up in nullspace somewhere.
Google is just too big as a company, and if they replaced every human in it with drones no one would know the difference. There is no human face or point of contact or any accountability and it’s becoming a problem.
My girlfriend was able to get on the phone with a tech support person for her small business ads and I was shocked she was able to even talk to someone at Google over a phone without being a major company with a big monthly bill.
The woman was still snarky to her and unhelpful but still a real human was available.
A lot of this has to do with our own perceptions and trust. Purchasing decisions are never fully rational or information complete.
> that doesn’t mean that GCP has any guaranteed future either.
Nothing has a guaranteed future.
> AWS and Azure won’t slow down development
As long as it's paying off, they won't, and AWS maybe for longer even if it isn't. But Microsoft is no stranger to making investments in offerings and letting them stagnate or outright killing them if they don't pay off.
While Google Reader might be the most popular of the tools, that got offline'd, doing so is a common pattern with Google. According to gcemetery.co[1] Google has already killed 164 products, with each one having an average lifespan of approx. 4 years.
Google is always building new data centers to handle traffic growth for their own services. GCP infrastructure wouldn't be turned off, but re-purposed for internal growth.
On the other hand the, in comparison tiny, cost that Google Reader and other was in the budget, would have given Google so much good will. It was in other words cheap positive PR.
Killing Reader was massive strategic blunder, which in fairness to Google was probably not obvious to see at the time. But then to repeat that with Maps API,Google+, Sketchup and Wave (perhaps wave was first) just cemented Google's untrustworthy reputation.
Sketchup?? Huh. Glad I didn't get into it, then. This is the first time I've heard that, and I thought I was up to speed with the stuff Google dropped.
It doesn't matter, a datacenter can always be repurposed for their own internal product lines.
To be perfectly honest, i would rather go with a company that provides cloud as one of their main products rather than a company that has it as one of their many products.
Google piled massive resources behind Google+ and look where that is.
Personally, I don't think Google will yank the cord on this entirely, but they may just stop piling resources into it and/ or significantly increase prices to ratchet up profits. They don't have to drop the whole cloud to really screw up a developers life, just screwing with one API I rely on can kill a product and they've already done exactly that.
The problem is with Google you just don't know what's going to happen. Microsoft and Amazon are both known and neither plays games with their products.
Yeah, GCP is not the same as Google Reader, more like Google Maps. But that one recently had some changes that royally fucked some businesses over by changing pricing and quotas, so maybe not so absurd after all.
Exactly. If they just don't improve their pricing in line with AWS/Azure (which means massive capital investment, always subject to economy shifts in the cost of money) then people will be looking to move.
All the cloud offerings are massively more expensive than owning/leasing unless you have large dynamic scaling requirements. There will be middleware in the future to allow cloud agile / hybrid operation, so maybe cloud compute will become more commodity, as opposed to the current Rolls Royce pricing. At that point will Google be interested? Depends how much marginal cost is involved compared to running data centers just for themselves.
Investments in data centers and infrastructure can mean that
the Google Cloud may live on, but different offerings in the cloud might change with little notice.
Even if they don't just "turn off", why would I want to invest in a cloud platform that only staff enough to keep the lights on, while there are cloud platforms out there that continue to provide new features to make my development process less painful?
Those datacenters don't only house GCP you know. I'd be willing to bet GCP only makes up a comparatively small portion of their datacenter computing resources.
>Google’s problem remains its reputation for turning things off.
I'd put it this way: Google has a reputation for turning things off, but its _problem_ is an inability to stop doing that, to commit to its users/customers. In other contexts this could be written in terms of addiction.
If I were Sergey and Larry, this would be the thing I'd be retiring over, and I'm not sure Suchar can change it.
If Satya Nadella could get Microsoft to move beyond its Windows-all-or-nothing pathology, someone in charge at Google (including the two founders that vote-control the entire company directly - they can de facto hand Sundar the power to act as he needs to) can trivially put a stop to the relationship commitment issues at Google.
Its far from trivial to change an entire corporate culture on a dime.
From everything we have seen of Google's culture, working on new projects is exciting and is absolutely the way to get promoted.
Doing maintenance work, especially on products that aren't wildly successful gets you no attention, no staff, no funding, and probably more than a little tongue waging.
The CEO cant just change all that with directives, even if they do something extreme like a "No Depreciations" policy, products are liable to be depreciated in all but name (Joe the intern takes care of it every 5th Tuesday, technically not depreciated) by sheer corporate momentum alone, nobody wants to be stuck with a dead fish, even if its now illegal to openly comment on how much it stinks.
It would require change at every level of Google to place value into fixing/improving existing projects, rather than all the glory going to greenfield development.
Considering the kind of "kingmaker" culture Google's mentality breeds, ie what gets me ahead is gathering resources to focus on my project, changing things to a setup where contributing to other peoples silos is welcome and common is going to be an extremely difficult prospect because virtually all the people with power inside Google got that way by carefully tending their fiefdom, they aren't just going to throw that all a way, no matter what any executive says.
Its far from trivial to change an entire corporate culture on a dime.
You can say that, but when it's a response to the fact that Microsoft did that EXACT THING on the the scale in which they did it your statement doesn't hold any water. Go back in time and walk onto the Microsoft campus in Seattle and tell anyone that will listen in say 1995, 1999, 2001, 2007, or 2012 that Windows licensing is a dead end and see if you don't get lumped in with the loonies talking about the end of the world.
To say that Google can't do it is more an indictment of Google's leadership as opposed to the enormity of the task. To thinking a company with a 934 billion dollar market cap (Alphabet) can't figure out how to do enterprise software support if it wanted to, what a joke.
“All teams will henceforth expose their data and functionality through service interfaces.
Teams must communicate with each other through these interfaces.
There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.
It doesn't matter what technology they use. HTTP, Corba, Pubsub, custom protocols -- doesn't matter. Bezos doesn't care.
All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.
I am not sure why you are saying Microsoft transformed, its still the same old one now trying to embrace Linux as it runs as the main workload on Azure instead of windows. This is just done for survival, otherwise Microsoft would have gone to irrelevance.
Windows and Office licenses are still the main driver for Microsoft, just with accounting tricks and office 360 made into cloud revenues. This is an investor story to jack up the stocks. They are no better than google when it comes to platform lock-in. On top of it having used Azure services, I can say without a doubt its inferior to Amazon and Google cloud experience.
Microsoft didn't transform it's just that enterprises who hold up upgrading Windows and Office did so after windows 7 debacle to Windows 10. This is just cyclical uptick, not really transformation, its just lucky Nadella. The only good thing Nadella did is, didn't take any disastrous decision to thwart the uptick by embracing Linux and trying open source, by understanding that if it's not done Microsoft will go the IBM path to irrelevance.
In the process Microsoft having an old relationship with enterprises helped them to move some workloads to Azure even though it is an inferior service, by supporting Linux and showing commitment to it for financial gain not out of goodwill towards open source.
Still today Microsoft relevance on mobile is due to its office products, otherwise it is as good as irrelevant on mobile application and development front. It's alive on mobile just due to proprietary platform lock-in to .NET. Now made it open source to try to increase the share as it's not as useful given the rise of nodejs, Python, rust and other platforms.
Windows has not seen a payed upgrade for 5 years - that is in itself a major change. We'll see if they continue on this road, but for now their announced plan is that there will not be a new paid update of Windows. This clearly cuts down on one of the revenue streams for Windows Licensing.
Microsoft is the largest single contributor to Linux development. They have a large hand in Kubernetes. .NET is open source and runs on Linux/Mac natively. They have released and are maintaining the most popular lite IDE/editor of the decade simultaneously for Linux/Mac/Windows, and it was open source from the start. MSVC has a Clang frontend.
That they are not relevant on mobile seems a non-sequitur. The discussion was on whether the Microsoft Windows-first culture has changed, and it clearly has. They have clearly embraced open-source as a good strategy for them, and are making massive investments in it.
I would also note that Azure, while having all sorts of unexpected limitations, is at least much more transparent about pricing than AWS. The Azure UI almost always includes pricing information on the resources you are creating, which AWS carefully segregates away.
This licensing does not apply to enterprise editions and volume licensing, I believe you are still looking at consumer market which Microsoft already lost to a Apple and lately google chromebooks.
The major revenue stream for Microsoft is still old long term licensing deal for office combined with windows and than related server technologies to support office applications.
The model changed from licensing+upgrade fee to new subscription fees. This can be office 360 subscriptions which get you office products and windows or volume license subscriptions. Depending on the type of subscriptions these are classified as cloud or windows and office revenue. Azure come into picture as those companies having volume licenses have applications in legacy .NET which they move to Azure.
Microsoft is supporting Linux today because they lost the battle of technical superiority and most of the azure workloads for supporting internal business apps run on Linux. They ported .NET to Linux just to have those old accounts do not move out of azure and Microsoft proprietary eco-system easily and move them to subscription with long term contracts.
Majority of the revenue effect you see is just because Microsoft abandoned product updates for old versions and forced customers to move to windows 10 and above by making old one economically very expensive. So Nadella was lucky because he got the benefit of the cyclical revenue increase due to enterprise upgrades which companies didn’t do for many years.
Obviously adoption of Linux as primary driver for Azure kept those old customers from moving out of Azure to Amazon or google, even though technically azure quality and services were inferior. A company will not move to amazon or google unless there is significant exponential gains. If the old vendor can still support and give something which is not bad but not the best, customer will still stay on and here Nadella was good not to bash Linux like Balmer.
Companies prefer to purchase services within an established contract than to go ahead and sign a new one with new provider and go through the bidding process.
Also .Net is synonymous with microsoft so there is no reason to trust AWS, it's not their priority, they are a Perl and Java shop in general.
AWS is always bragging that they have twice as many Windows VMs than Azure.
AWS a Perl shop?
All of AWS services treat C# .Net Core as a first class citizen.
- CodeBuild has prebuilt C# .Net Core images for building apps. For licensing reasons they don’t have prebuilt Windows/Framework containers but their instructions are so clear that I was able to build one before I knew anything about Docker
- Lambda has native support for .Net Core 2.x and the C# SDK for AWS has a template to build a custom runtime for C# 3.x
- Speaking of which, the AWS SDK and plug-in for C#/Visual Studio and the corresponding Nuget packages are excellent and fully featured.
- The CloudFormation Developer Kit supports C#
- There are CodeStar and ElasticBeanstalk getting started templates for .Net Framework and .Net Core
AWS was built to support Amazon website which is built in Perl and still internal AWS core code might contain perl. Probably over the years they might have moved slowly to Java. I don't work for AWS so can't say much.
Regarding support for .NET whatever AWS does microsoft will always be way ahead of them. Microsoft is not elastic.co that AWS leech on and put the original guys on the side and don't contribute back. AWS is really like a leech on open source now trying to leech on Kubernetes.
They can do this with small open source project, not with the projects supported by google or Microsoft. Like when it comes to Kubernetes AWS is playing catch with Google. So AWS Fargate and other services are still inferior to Google managed K8s. Indeed microsoft at present is ahead of AWS in managed kubernetes services. Its just the initial head-start and developers who are familiar with AWS proprietary API's find it hard to believe that in such a short time the skills they learned is no longer cutting edge and google or microsoft proprietary API's overtaken them in performance and ease of use.
AWS was never built to support amazons website, it was never the result of amazon.com's internal code-base of "hosting" getting made public, it was never amazon's excess peak server capacity, etc, it had virtually no relation to the hosting of amazon.com at all, it was an independent project that might have benefited from a lot of the general design principles of how amazon.com was built, but that is it.
All of these things are widely believed myths that have little to no basis in reality.
It certainly was not designed as some kind of Perl hosting environment.
It didn't even host Amazon.com at all until many years after the fact.
I did use AWS for good 5 years and every time it's been inferior, e.g. launching times of EC2 instances were double that of Google Cloud, better than azure though (might have changed with new instance type may be), N2 and N1 instances in gcp are usually faster in start, stop delete cycle than AWS as recently as last week. Networking stack between regional nodes is not as performant with higher latency than google cloud with its andromeda network stack, on top its more expensive than google and microsoft for bandwidth. Even though I put critical comments for GCP on this article, I feel AWS fare no better, indeed I feel its worse.
I have yet to see any good open source project by AWS team in the wild like Kubernetes, Linux Kernel Namespaces and Cgroups, Map Reduce from Google or .NET from Microsoft. So far what I have seen is that AWS just leech on other open source like PostgreSQL to build Aurora and RDS service without really contributing back to PostgreSQL, because postgreSQL comes with BSD license AWS can just leech on it. Same for elastic search and many other open source they leech on. I am still waiting if they are really just leechers or giving back to the open source community. Like Amazon Redshift is based on an older version of PostgreSQL 8.0.2, and Redshift has made changes to that version [1], but nothing is made open source because BSD license do not require it. This is just one big example but there are many. For open source community and contributions I feel Google and Microsoft are much better than Amazon and AWS by miles. It's just that due to early start AWS is reaping benefits by leeching on open source.
It seems like you were much more on the infrastructure side than the development side. The discussion was about .Net. What was your experience with the SDKs to judge where AWS was behind MS supporting it?
How does open source help an end user who is deciding which cloud provider to use?
AWS is infrastructure as a service with some priorietray API's to provide platform to build applications. These platforms are build from open source projects which does not have GPLv3 or AGPL license. So AWS is largely an IaaS service not really a platform, open source library or system development company like Google or Microsoft.
AWS does not develop .NET SDK, as I mentioned in my earlier post there is no contribution of AWS in development of .NET, so they just provide infrastructure support of what ever Microsoft and the open source community releases.
In general microsoft acts as a steward to develop .NET and related infrastructure on Azure, then AWS copy and launch it as .NET infrastructure as service. They play catch up with Microsoft in this area.
I will stand corrected if you can show me that AWS (i.e. Amazon) has active open source .NET framework core developers in their internal team developing and enhancing .NET SDK or CLR open source versions.
They do the same with AI and ML Services. It is built using TensorFlow, sci-kit learn, pytorch, CNTK and various python and C++ open source libraries. Again I have yet to see example of AWS (i.e. Amazon hiring core developers of these libraries and release open source versions). They don't develop these libraries just leech on it to create it's own API's. I have yet to see any framework from AWS like TensorFlow, Keras, Pytorch and CNTK.
Again, the discussion was about AWS being behind Azure with respect to support for .Net. When deciding which cloud provider one should go with, why should I care as an end user which company did more for open source?
There is nothing to copy as far as .Net. Microsoft releases a new version of .Net, all AWS has to do is make sure that its SDK’s support it. But there usually aren’t any breaking changes.
As far as the other services that I could see needing to support, the only ones that I can think of is CodeBuild and lambda. For those two, you can create custom Docker images and runtimes respectively.
> I am not sure why you are saying Microsoft transformed, its still the same old one now trying to embrace Linux
I'm one of those persons who upsold friends, families and at least one boss on to use Linux.
I'm not a business analyst but I can say that Microsoft has transformed. I still prefer Linux as does a number of fellow sysadmins and developers, but Microsoft has changed to the point where they are not a problem to us anymore. Azure portal works equally well from Firefox on Linux as from Internet Explorer or Edge on Windows.
> as it runs as the main workload on Azure instead of windows. This is just done for survival, otherwise Microsoft would have gone to irrelevance.
The best reason for transformation in fact: because the subject realizes it is in their own best interest to change and it improves their situation.
> Windows and Office licenses are still the main driver for Microsoft, just with accounting tricks and office 360 made into cloud revenues.
I don't know.
> This is an investor story to jack up the stocks. They are no better than google when it comes to platform lock-in. On top of it having used Azure services, I can say without a doubt its inferior to Amazon and Google cloud experience.
I've used Amazon (two years, narrow experience) and Google Cloud (two years, broader but possibly shallower experience, certified) and now Azure lately.
So far, inferior is not the word I would use. I'd possibly stick with different or something neutral.
One great book on how the culture of an entire giant company can change is "Who says elephants can't dance" by Lou Gerstner. He was the CEO of IBM who orchestrated IBM's transformation from a mainframe supplier to a service-oriented company. My take on the process is this - the change can be done and has been done when there is an existential crisis. The crisis may not be apparent from the outside, but company internals can notice a terminal decline of their core product/service and has an impetus to change the direction. Even then, it's not easy. I would argue that Microsoft had to make somewhat of an about-turn from Windows because first the Internet and second the Cloud was putting pressure on their core business threatening to make the OS a marginal player. I don't think Google is in that position, at least not yet. Google Ad business is not facing any terminal threat. Thereby it is much harder for Google to make a culture change because simply the pressure to make the change is not there at an organizational level.
[Edit: Prepositional corrections]
They're already there on my part. Between their firing employees who organize or complain that their corporate slogan apparently now is "Be Evil", their chaotic product decision making, and their toxic internal politics, I have absolutely no interest in working for Google. Furthermore, I've noticed that the Google workforce seems to be becoming less.... Googly.... recently (disclaimer: I work down the street from the Googleplex and see many Googlers as they do their daily migrations). As in, they're now hiring a broader selection of people who aren't just the top 5% in class. What that tells me is that they're having more difficulty on the recruiting front and having to cast their net wider.
When I first wrote that sentence, I said "until people", but it occurred to me that being shunned by a small group of engineers probably barely registers on any metric that a large company would pay attention to. It wouldn't be actionable until the well had been running dry for a while.
I mean, shit, I work at a place where many of my favorite people have moved on to other things, few have been replaced, and yet we're only just having sincere conversations about how to fix our culture problems. That had to wait for one of the ringleaders to quit.
So far as I can tell from my minuscule keyhole, Sergey and Larry are the ringleaders. They'll never quit, and it'll take hitting rock bottom for them to have a change of heart. Not unlike Microsoft, after their stock began to tank.
Every major tech company has changed its culture based on a changing landscape.
Apple - look at Apple’s revenue and profit mix over the past 10-15 years its apparent that they were able to change. Of course the change after Jobs came on is well known.
Microsoft - was “Windows first” during the Balmer era.
Facebook - was in danger of being made irrelevant after mobile. They were making a lot on games hosted on their platform.
Amazon: AWS and their move toward services even internally.
Netflix: went from shipping DVDs and had to become a tech company in the era of streaming.
Your comment really resonates with me. I worked at google for many years and I eventually got tired of exactly that. Inside the company we complained about all the problems they still have, canceling projects, no way to talk to a human not even paid support to talk about your whatever being turned off. It was really irritating.
I think Google needs to explicitly spin out a Google Product company that is customer focused and develops/maintains/supports platforms and applications. It would be distinct from Search and Ads and would instead sell them (and other customers) access to Google data centers and GCP.
I think Google needs to explicitly spin out a Google Product company that is customer focused and develops/maintains/supports platforms and applications.
Honestly, and I'm more of a Google side-eyer than a hater, but I'm not sure they're capable of this, it's just not in their DNA. I've been saying "Google is bad at product" for a long time, like a "high PR" long time, and this mindset has been greeted with continual killoffs and usability stumbles (current Android is kind of a mess UI-wise, e.g.).
I simply don't think they're capable of putting a division together that could be relied upon. Heck, Alphabet might simply kill that off after a few years!
Another perception is that of killing hierarchies of user accounts / pulling rugs on projects e.g. if links are established between adding someone who once broke the rules and whatever they might be working on now, with no way of reaching someone human for support...
... where one of the few ways of rectifying the situation is to get a top posting on HN in the hope that a Googler will see your plea for help.
I mean, that's probably mainly related to Android dev but I've seen plenty of stories to support that feeling:
My perception might be misguided / influenced by being in a perception bubble, however that is my reality and AWS or AZURE just seems a whole lot safer. So, why should I as a developer invest any time in GC? I did attend a Google dev day re machine learning++ in Melbourne a couple of years ago, and the products seem nice and all, but the competition isn't exactly lagging behind.
My recommendation would be to really address this issue of human support and trust.
Also AWS is just the best at marketing their services. They did what Google did with search. We always say we "Google" things.
Developers these days say "Chuck it in S3" or "Run it on EC2". I feel they have a strong advantage because they've kind of come to own the language of the cloud.
Developers these days say "Chuck it in S3" or "Run it on EC2". I feel they have a strong advantage because they've kind of come to own the language of the cloud.
After many years of working with AWS almost exclusively, I recently started a new $DAYJOB where our primary public cloud provider is Azure. A couple of days ago I was chatting with a co-worker about something, and he literally says "I think we should just chuck it in S3 and call it good" (paraphrased slightly, due to my imperfect memory).
It struck me as odd for a few seconds, and then I realized that exactly what you are talking about has taken place. S3 is so dominant that it's become the default label for object storage in the cloud.
Actually, most of the time we say "in the cloud" rather than naming a specific hosting provider. Definitely Amazon has the first mover advantage and accumulated reputation first, but it's hardly unassailable.
Still... I think the bigger problem isn't whether or not Google plans topull the plug or not, but that it has a reputation of pulling plugs to such an extent that people factor that into a decision of using their services.
When it's something as big a choice as a cloud provider that can cast a long shadow over their offerings.
In addition, I remain cloud agnostic as well. As a student, I stick to whichever platforms can give some free credits. At the moment I have some cloud infra on google and some on aws.
That’s a good thing not to tie in to proprietary api’s, indeed every cloud provider is doing it and after Google’s recent management shuffle to bring in management from Oracle making them alike.
Try using apache-libcloud to make your deployment and programs cloud agnostic. Also try using smaller alternatives like hetzner or scaleway.
Once you go down this cloud rabbit hole you will be hold hostage to whims of these providers, where they can shutdown any service at their will or ask to pay an arm and leg. Also try to have non USA cloud providers as another backup option in the long run.
Amazon and Microsoft are much better at support though. I doubt you’ll see a lot of Google cloud in the European public sector where I work for instance. Google simply doesn’t know how to work with us or give us the reassurances we need to trust them.
I’m by no means a AWA or Azure fanboy, I’m on the team that hopes we get a solid European alternative, but until we do both Amazon and Microsoft are leagues ahead of Google.
I remember vividly talking to a GCP saleswoman. I was asking her about technical things and process/pricing and she just kept saying things like "We're talking with $FIRSTNAME about that." And I was like, 'who is this $FIRSTNAME guy?' and then I realized it was the CTO. This guy is so far divorced from anything technical or policy it's absurd, he just produces content for his 1- and 2- up bosses to look good in press releases, and he has no input to the way anything is done. But GCP had identified him as the way into the organization, and was totally uninterested in engaging with anyone else other than giving away swag.
Contrast this with AWS. They have expert engineers, pre- and post- sales, helping you find good ways to solve your problem. I could ring a senior guy on his cell right now if needed. The only problem with AWS is cost and complexity, it's the fast path to developing a $20k/day cocaine habit. But the AWS dealer will definitely come to your house to deliver at 11pm.
(It is a bit of a change from 10 years ago though, when everything had to be paid by credit card. Gave the accountants a heart attack. Gave me an ulcer from thinking about everything halting because the fraud control might reject the bill without warning...)
Azure definitely isn't in that league, still want to sell to the whole enterprise, getting promo stuff requires them to sign off at five levels, lawyers are involved in everything. In short, their dev relations are shite.
To illustrate your point about AWS, at my own workplace there are a few AWS people who are actually in our office once a week, sitting nearby just so they can be easily available to answer questions and work with us to design our architecture or assist in troubleshooting issues. I honestly can't imagine Google providing that level of dedicated support.
Google’s problem remains its reputation for turning things off.