←back to thread

Use One Big Server (2022)

(specbranch.com)
343 points antov825 | 2 comments | 31 Aug 25 17:29 UTC | HN request time: 0s | source
Show context
matt-p ◴[31 Aug 25 18:11 UTC] No.45085454[source]▶
A thoroughly good article. It's probably worth also considering adding a CDN if you take this approach at scale. You get to use their WAF and DNS failover.

A big pain point that I personally don't love is that this non-cloud approach normally means running my own database. It's worth considering a provider who also provides cloud databases.

If you go for an 'active/passive' setup, consider saving even more money by using a cloud VM with auto scaling for the 'passive' part.

In terms of pricing the deals available these days on servers are amazing you can get 4GB RAM VPSs with decent CPU and bandwidth for ~$6 or bare metal for ~$90 for 32GB RAM quad core worth using sites like serversearcher.com to compare.

replies(2): >>45086101 #>>45086515 #
railorsi ◴[31 Aug 25 19:57 UTC] No.45086515[source]▶
What’s the issue with running Postgres inside a docker container + regular backups? Never had problem and relatively easy to manage.
replies(2): >>45086789 #>>45095728 #
1. Biganon ◴[01 Sep 25 19:19 UTC] No.45095728[source]▶
Why use a docker container? I run Postgres as is, what would I gain with running it in a container?
replies(1): >>45096384 #
2. Nextgrid ◴[01 Sep 25 20:33 UTC] No.45096384[source]▶
It makes the whole thing is configured in a docker-compose file (or your raw Docker CLI invocation) + the data volume. So as long as you have those two things you can replicate it and move it to other hosts regardless of their distro.

Compare that with using your distro's packaged version where you can have version variations, variations in default config or file path locations, etc.