The audacity of ranting about some cloud provider leveraging their licensing and then dropping a link to Azure in the next sentence, I love it, thanks Google.
Removing data transfer fees when moving off Google Cloud
101–110 of 113 posts
Re: Removing data transfer fees when moving off Google Cloud
#102Earlier quoted context omitted.
"Egress can be no more expensive than ingress" seems like a reasonable rule.
But not during normal operation when egress to consumers is in higher demand than ingress. This would raise ingress prices unnecessarily.
For what the lock-in topic is concerned the expensive egress is just relevant when you want to leave your provider, not during daily operations with your consumers. Free ingress but prohibitively expensive egress is literally only there to make it as easy as possible for customers to come to the cloud provider and as hard as possible to leave. Coming to a provider or leaving them should cost the same or else it's just a trap.
This is like Comcast giving you the initial installation for free but charging you an arm, a leg, and a year of your life to allow you to leave because "the process is costly". Both practices are scummy and abusive towards the customer.
Re: Removing data transfer fees when moving off Google Cloud
#103RIP Google Cloud
calling it now
Re: Removing data transfer fees when moving off Google Cloud
#104RIP Google Cloud calling it now
Let's hope not, most of their business will move to Azure, and is that ever a dumpster fire.
Re: Removing data transfer fees when moving off Google Cloud
#105Re: Removing data transfer fees when moving off Google Cloud
#106Hi. I fix AWS bills for a living and also shitpost a lot. This is a smart play that costs them basically nothing. Remember that egressing data costs customers at worst 3x the monthly cost of storing it. Nobody is avoiding leaving because of the egress fee. What this does do is assuage the “lock-in” fear common in cloud-reluctant customers, while presents them as being forward thinking. I’ve never heard of a cloud mig…
I share the view that nobody avoids an exit or migration because of egress fees. In fact, for online migrations the period of replicating data between providers might go on for months.
But all cloud providers leverage The Principle of data locality or data gravity, which states that compute benefits from being close to the stored data. If a customer moves the data elsewhere it follows that the compute will soon leave too.
Re: Removing data transfer fees when moving off Google Cloud
#107The cynical might wonder if this is a precursor to Google closing down its cloud. They can't really shut Google Cloud down and still be charging people to exit. And if they had suddenly seen the light on egress fees then surely they would have cut egress fees everywhere..... the fact that it's only on account closure is kinda suspicious.
Shutting down a $30B+ business would be such a ridiculous, yet Google-esque decision. It would also be a huge shame for consumers - the public cloud is already an Oligopoly
There's always Oracle (/s)
Re: Removing data transfer fees when moving off Google Cloud
#108RIP Google Cloud calling it now
Let's hope not, most of their business will move to Azure, and is that ever a dumpster fire.
I think Azure is great if you are willing to do it Microsoft's way and are focused on B2B markets where factors like compliance matter in a way that can actually disrupt your sales cycle.
Put differently, if you can get over the principled nerd stuff like "everything must be open" and break out that wallet, you can stand to make a lot of money without as much headache as the guy who decided to roll his own IdP.
Getting "cost sensitive" on Azure is how you lose track of the rabbit. The whole point in my view is to trade money for reduced complexity and time. It lets you focus on solving really hard business that others simply can't seem to find the time to.
Re: Removing data transfer fees when moving off Google Cloud
#109Earlier quoted context omitted.
The whole word smacks of Bellhead thinking. With ethernet you put a frame on the wire and hope.
The term “non-blocking” may well originate with circuit switching, but Ethernet switches have referred to the behavior of supporting full line rate between any combination of inputs and outputs as “non-blocking” for a long time. (I wouldn’t call myself an expert on switching, but I learned IOS before there was a thing called iOS, and I think this usage predates me by a decent amount.) > With ethernet you put a frame…
[deleted]