I&#x27;ll add that it isn&#x27;t just data egress. It&#x27;s also inter-AZ transfer which costs $0.01&#x2F;GB. But it&#x27;s really $0.02&#x2F;GB since you get charged 1 cent for the traffic leaving and 1 cent for the traffic arriving on the other side.If you&#x27;re running in AWS, you want to have servers in multiple availability zones in the same region so that if one AZ goes down you&#x27;re still up. Let&#x27;s say you&#x27;re running your APIs and Kafka in two AZs (us-east-1a, us-east-1b). A user hits your API in 1a and you publish a message to Kafka. You need to write to 3 boxes. On average, you&#x27;re paying $0.03&#x2F;GB for your Kafka writes - $0.02&#x2F;GB when the API server is in the same AZ as two of the quorum and $0.04&#x2F;GB when the API server is in the same AZ as only one of the quorum.That&#x27;s 30x what Hetzner is charging for internet egress from its US data centers. People here were outraged that Hetzner would charge $0.001&#x2F;GB for internet egress while using AWS is costing 30x that for transfer in the same region. Plus, a lot of companies use 3 AZs (so that they still have high availability if one AZ goes down). Then you&#x27;re paying the $0.04&#x2F;GB on all writes.And this doesn&#x27;t just apply to Kafka. Let&#x27;s say you&#x27;re running PostgreSQL with standbys: you&#x27;re paying for all that data transfer from the API nodes in other AZs to the leader node and all that data transfer to replicate the writes to the standby nodes. When reading, you could do AZ-aware reads from the standby nodes if you don&#x27;t need the latest data to avoid charges.At some point, it feels like we&#x27;re spending a lot of time and effort trying to minimize cloud costs - costs that we don&#x27;t have to worry about from traditional datacenter providers. The cloud was supposed to make things easier, but the costs have made a lot of stuff harder.And I&#x27;m not saying that AWS should charge nothing for inter-AZ traffic - they&#x27;re just charging way too much. I don&#x27;t know how much it really costs to service that traffic, but Hetzner can send the traffic over the internet for $0.001&#x2F;GB from data centers that they don&#x27;t own. It feels like Amazon should be able to send that traffic down the road for a good bit less than that. I believe in charging customers for what they&#x27;re using so that you don&#x27;t have bad actors exploiting pricing loopholes - but Amazon charges an absolute fortune for stuff that&#x27;s relatively cheap.

It&#x27;s a great start, but it&#x27;s missing the silent killer: data transfer!AWS egress data transfer pricing is 100-1000x the price of equivalent IP Transit. (Yes, I am not exaggerating.) It is so significant that I&#x27;ve seen data transfer account for &gt;90% of 7-figure AWS bills. Given enough spend, that alone is enough to make the business case for a migration.

As someone who works for a company that’s transitioning out of the cloud into their own data centers, the supply chain factor is difficult. You have to be really good at forecasting and planning with a large upfront cost. But the savings are substantial (up to 70%)

That&#x27;s always a possibility, but let&#x27;s say you&#x27;re running a cluster of 100+ machines. One dies and it&#x27;ll be 24 hours to get a replacement. That&#x27;s not such a big deal - your capacity is only down 1% and you aren&#x27;t running stuff at 95%+ utilization.If you&#x27;re running 1 box, you might have a point. If you have 100 boxes, you could pay for a couple spare boxes and still save a ton of money. If you&#x27;re paying $700&#x2F;mo&#x2F;server for AWS and bare metal would cost you $100&#x2F;mo&#x2F;server, you could have a few spare metal servers and still pay a ton less. 100 servers * $700&#x2F;mo = $70,000. 103 servers * $100&#x2F;mo = $10,300 - the &quot;extra&quot; $300 is kind of a rounding error.Even if you&#x27;re running 5 servers, $700 * 5 servers = $3,500; $100 * 10 servers = $1,000. You literally have a spare server for every box in your cluster. Heck, even if you&#x27;re running 1 server, $700 * 1 server = $700; $100 * 3 servers = $300. You have double the number of backup servers already online for less than half the price. Instead of running PostgreSQL, having a server go down, and then restoring from a backup to a brand new cloud box, you could literally have 2 hot standby servers and still save money.Yes, bare metal isn&#x27;t instant like the cloud - but if they&#x27;re charging you 7x more than bare metal, you could literally have 2 backup servers for every 1 server and still save a ton of money. You&#x27;re not paying an extra 10% or 20% for the cloud&#x27;s flexibility or ease of replacement. You&#x27;re many several times more for every server - to the point where you could just purchase 3x or 5x with bare metal and just have some of it laying around idle.

Exactly! When your savings are 2-3x per unit, you have more room in the budget to over-provision. Now you have increased headroom for growth, and improved redundancy.

Why do you only have _one_? Get two or three. :-)

I&#x27;m always tempted. But then I think about if my one bare metal servers dies how long will it take me to get a replacement? Maybe this has improved over the years but I recall with bare metal there can be 24 hours or longer to get a new one.

I missed the cost of the network gear.

How much does The Cloud really cost?