←back to thread

Replacing a $3000/mo Heroku bill with a $55/mo server

(disco.cloud)
804 points jryio | 1 comments | 21 Oct 25 20:28 UTC | HN request time: 0s | source
Show context
Nemo_bis ◴[22 Oct 25 05:48 UTC] No.45665301[source]▶
> And while Hetzner's price-performance is exceptional, its limited presence in the US was a consideration; for this staging workload, it wasn't an issue, but it's a factor for production services targeting US users.

What is this referring to? Concerns about capacity if you need to scale up quickly? Or just "political"/marketing considerations about people not being used to being served by a Hetzner server?

replies(3): >>45665326 #>>45665328 #>>45666170 #
andmarios ◴[22 Oct 25 08:13 UTC] No.45666170[source]▶
I guess it's latency and data residency.
replies(1): >>45666236 #
1. gregsadetsky ◴[22 Oct 25 08:23 UTC] No.45666236[source]▶
Correct! Re: latency, as I just noted elsewhere, if you run your prod database using Crunchy Bridge or Supabase or another big provider (which you absolutely should for prod), that typically means that your db will be running within an AWS region. You would, in most cases, need to run your compute in the same region. So yeah, at that point, Hetzner would be out.