←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.409s | 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 #
odie5533 ◴[21 Oct 25 21:04 UTC] No.45661694[source]▶
I think OP is using these less as staging and more as dev environments for individual developers. That seems like a great use of a single server to me.

I'd still like a staging + prod, but keeping the dev environments on a separate beefy server seems smart.

replies(1): >>45661739 #
1. ricketycricket ◴[21 Oct 25 21:09 UTC] No.45661739[source]▶
I've been using a development server for about 9 years and the best thing I ever did was move to a machine with a low-power Xeon D for a time. It made development painful enough that I quickly fixed the performance issues I was able to overlook on more powerful hardware. I recommend it, even just as an exercise.
replies(1): >>45663527 #
2. eru ◴[22 Oct 25 00:22 UTC] No.45663527[source]▶
For similar reasons, in the Google office I worked in you had the option to connect to a really intentionally crappy wifi that was simulating a 2G connection.