←back to thread

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

(disco.cloud)
804 points jryio | 2 comments | 21 Oct 25 20:28 UTC | HN request time: 0.001s | source
Show context
tempest_ ◴[21 Oct 25 20:54 UTC] No.45661573[source]▶
The cloud has made people forget how far you can get with a single machine.

Hosting staging envs in pricey cloud envs seems crazy to me but I understand why you would want to because modern clouds can have a lot of moving parts.

replies(11): >>45661597 #>>45661608 #>>45661636 #>>45661649 #>>45661714 #>>45661726 #>>45661756 #>>45661835 #>>45662162 #>>45662794 #>>45663024 #
odie5533 ◴[21 Oct 25 20:56 UTC] No.45661597[source]▶
Fully replicating prod is helpful. Saves time since deployment is similar and does a better test of what prod will be.
replies(1): >>45661657 #
teaearlgraycold ◴[21 Oct 25 21:01 UTC] No.45661657[source]▶
Completely agree. It’s not a staging server if it’s hosted on a different platform.
replies(2): >>45661694 #>>45661797 #
1. hamdingers ◴[21 Oct 25 21:13 UTC] No.45661797[source]▶
The "platform" software runs on is just other software. If your prod environment is managed kubernetes then you don't lose much if your staging environment is self-hosted kubernetes.
replies(1): >>45661814 #
2. odie5533 ◴[21 Oct 25 21:15 UTC] No.45661814[source]▶
Load balancers, IAM roles, kubernetes upgrades, postgres upgrades, security settings, DNS records, http routes... there's a lot that can go wrong and makes it useful to have a staging environment.