Live data from Hacker News

Cloud Egress Costs

getdeploying.com

81–90 of 318 posts

Re: Cloud Egress Costs

#81
post #64

Offt, not a good look for Railway, Render or Vercel!

I’m a fan of all three, but my mindset is that I’m not just paying for raw infrastructure, I’m paying for the engineering work I don’t have to do when I use them.

I’m a fan of them too. Their pricing gives me a “we will punish your success” vibe. I suppose that’s preferable to paying through the nose for not scaling.

Re: Cloud Egress Costs

#82
post #65

Oracle Cloud only charges a fraction of want Google, Microsoft, and Amazon charge. Any idea how Oracle is able to keep the cost so low? Or are the others just inflating the price so customers don’t move to the competitor? In that case Oracle deserves a shout out for not applying these vendor lock-in practices.

Hetzner charges $1/TB. Oracle charges $7/TB, AWS $90/TB.

Oracle has probably really good margins on egress costs. With AWS/GCP/Azure the costs are absurd because for a lot of their customers it's not a big cost during operation, but makes moving data off cost prohibitive. It's simply a vendor lock-in mechanism for them.

Re: Cloud Egress Costs

#83

The article says “ Cloud providers charge for egress because it costs them money to send data out of their network. They have to pay for the infrastructure and bandwidth required to send data to users”. The charge is not based on cost in the case of the big names. They charge an arm and a leg because they want to keep you and your data on their platform. When you move it you are breaking free. Hence the high costs to…

It also forces downstream vendors that ingest a lot of data (e.g datadog, snowflake) to maintain cloud presence because their customers will not to want to pay egress fees

Re: Cloud Egress Costs

#84
post #41

The cost of egress traffic is a very good reason for many organizations to not fully migrate to a cloud provider anytime soon. And since, unlike with storage costs, there doesn't seem to be an actual reason (other than: it makes migrating to competitors cost-prohibitive in a subset of cases), that seems kind of... weird? Small example: an actual company I do some work for is in the business of delivering creative ass…

> other than: it makes migrating to competitors cost-prohibitive in a subset of cases My theory: it forces third party services into the same cloud. Suppose you use AWS and you want to pay a third party SaaS provider for some service involving moderate-to-large amounts of data. Here’s one of many examples: https://www.snowflake.com/en/data-cloud/pricing-options/ And look at this remarkable choice: you get to pick AWS…

It's pretty simple. Excessive egress costs = vendor lock in, and yes, forcing third party services into the same cloud (the walled garden), and limiting customer choice.

Just another reason so many orgs are getting heartburn from going too deep too fast into the cloud.

Re: Cloud Egress Costs

#85
We moved to AWS a few years ago, after self-hosting our own storage for years. What a nightmare.. The egress fees were killing us, so we had to find something else. Being weary of these large tech companies, and being that these days we're more privacy conscious as well. We found a new startup that outsources storage nodes to individuals / businesses. You have to install what they call a "relayer" on prem. The relayer is the S3 endpoint. It breaks up the data and encrypts it before sending each piece to a different node on the network. No centralized behemoth holding us hostage over our data and no egress fees. We're a smaller company, so I was able to talk them into trying it out. I doubt you'd be able to talk an enterprise into using a lesser-known technology though.

Re: Cloud Egress Costs

#86
post #65

Oracle Cloud only charges a fraction of want Google, Microsoft, and Amazon charge. Any idea how Oracle is able to keep the cost so low? Or are the others just inflating the price so customers don’t move to the competitor? In that case Oracle deserves a shout out for not applying these vendor lock-in practices.

The margin on egress is insane. Oracle got into cloud late in the game and burned a lot of goodwill downmarket so they have to sacrifice that to play catchup

Re: Cloud Egress Costs

#87
post #25

Earlier quoted context omitted.

My feeling is that egress is easily measured, so it's where costs that are hard to assess get moved to. It doesn't feel great to be line item billed for stuff at 10x the rate of credible other offers. I think there is also some geo-specific pricing that gets hidden in a global price; bandwidth can be a lot more expensive in some locations than others and if you are charged 5x for egress in south america, nobody will…

Right. Egress is an imperfect, but reasonable metric for overall utilization. If they started charging for CPU hertz above a certain threshold, that'd be a harder sell.

I mean, they kinda already do depending on your plan (see: AWS EC2 spot instances)

Re: Cloud Egress Costs

#88
post #76
post #46

Earlier quoted context omitted.

I don’t believe this. Operating an internal cloud network is expensive , but it’s expensive because of internal traffic, and they don’t charge for that internal traffic. Egress is just like traffic to any other system, and AWS doesn’t charge for that. Also: > It doesn't feel great to be line item billed for stuff at 10x the rate of credible other offers. It’s quite a bit worse than 10x

AWS charges for internal traffic too, both cross-az and cross-region.

The inter-AZ charges kill me. They’re charging you for traffic over what is almost certainly private fiber, of a distance no more than 50 miles or so. Just absurd.

Then, they have the audacity to recommend you make everything Multi-AZ. “Don’t worry, RDS-RDS traffic isn’t billed!” Yes, but the apps running in us-east-1a that are hitting -1b and -1c due to load balancers most assuredly do bill for traffic.

Re: Cloud Egress Costs

#89
post #47
post #41

Earlier quoted context omitted.

> other than: it makes migrating to competitors cost-prohibitive in a subset of cases My theory: it forces third party services into the same cloud. Suppose you use AWS and you want to pay a third party SaaS provider for some service involving moderate-to-large amounts of data. Here’s one of many examples: https://www.snowflake.com/en/data-cloud/pricing-options/ And look at this remarkable choice: you get to pick AWS…

Snowflake's margins are like 90%+ on top of the compute they sell, and they pass on all these costs including egress directly to customers.

That's not the point. The point is that if the customer and SAAS provider "happen to" be in the same cloud then nobody pays any egress costs, but if the provider operated out of their own datacenter then the customer would pay additional egress costs to AWS to export their data to the SAAS provider. Snowflake is a good example because by the nature of the business customers send them a lot of data. This not only makes the customer pay more, but it also makes their billing and cost accounting much more complicated and unpredictable.

Re: Cloud Egress Costs

#90
post #43
post #30

Earlier quoted context omitted.

Definitely lucrative enough. The use case you've described isn't particularly uncommon, but lots of companies just pay for the egress. The problem is that there are now multiple generations of software engineers that do not know how bandwidth is priced. They've only used managed providers that charge per unit of ingress/egress, at some fractional dollar per GB.

I’ve had people refuse to believe that bandwidth is actually very cheap and cloud markup is insane (hundreds or even thousands of times cost). I show them bare metal providers and colo that bills by size of pipe rather than transfer. They refuse to believe it or assume there must be a catch. There usually isn’t, though sometimes the very cheapest skimp on things like rich peering and can be slightly slower or less re…

Cloud providers have done an incredible job creating an entire generation of people who have no knowledge of such things.

$0.09/GB? I guess that’s just what it costs. Expected when you’ve never looked at, considered, or even heard of things like peering and buying transit or even co-location. Enter 95th percentile billing on a gig port for $500/mo or whatever…

Same goes for hardware. Want to watch something glorious? Take someone who has only ever used VMs, etc in big cloud and give them even a moderate spec new bare metal server. The performance melts their brains.

Then they realize the entire thing - colo, servers, bandwidth, even staff is a fraction of the cost.

Post reply on HN