We cut costs by 70% by moving from GCP and CockroachDB to Hetzner and PostgreSQL • Hacker News Board

Re: We cut costs by 70% by moving from GCP and CockroachDB to Hetzner and PostgreSQL

#71

Post by LorenzoGood » Sun, Apr 14, 2024, 4:05 PM UTC

everforward wrote: post #32

paxys wrote: post #22

Earlier quoted context omitted.

You can get declarative deployments via a systemd config. If you really want to use Docker then use a Compose file. If jobs are what you are concerned about then I can assure you no company is skipping on software developers because they don't know Kubernetes syntax.

That doesn't capture the same thing. It doesn't capture volumes, versions of binaries, nginx/postgres/whatever configs, etc. Ansible/Salt/Puppet/Chef/CFEngine are closer comparisons.

For this, you can use nix with deploy-rs, and define those configurations declaratively.

Re: We cut costs by 70% by moving from GCP and CockroachDB to Hetzner and PostgreSQL

#72

Post by scrubs » Sun, Apr 14, 2024, 6:47 PM UTC

windexh8er wrote: post #50

paxys wrote: post #7

It's wild to me that we are talking about a site running on a single 2 core VPS costing $15/mo and the developer didn't stop to consider that maybe they don't need Kubernetes for this. Like...just run your damn services on the box like we've been doing since web hosting first became a thing.

I've said it a few times before: k8s is such a distraction for so many startups I've been in (~5). All of them fall into the same trap: write entire arch around k8s and then not really invest the engineering into building it out fully. Instead they all seemed to settle on "hey this works" which kicks off the technical debt receipt printing. In all of them fixing things often went like this... * A: XYZ is broke. * B:…

Let's put k8s aside. If I had a complex system needing say five boxes, I might be able to admin it well - startup, shutdown, upgrade - if there was a simple orchestrated glue between the boxes e.g. on the control box 1, run a script to start daemons/pids on boxes 2, 5 which blocks until success or failure ... something more sophisticated than remsh/ssh. This is old school, but it's just a script or three.

Re: We cut costs by 70% by moving from GCP and CockroachDB to Hetzner and PostgreSQL

#73

Post by everforward » Mon, Apr 15, 2024, 1:39 PM UTC

lolinder wrote: post #38

everforward wrote: post #32

Earlier quoted context omitted.

That doesn't capture the same thing. It doesn't capture volumes, versions of binaries, nginx/postgres/whatever configs, etc. Ansible/Salt/Puppet/Chef/CFEngine are closer comparisons.

With Docker Compose you can define volumes, versions, and configs can be volumes that point to a file that lives alongside your compose.yaml.

Sure, depending on how you want to draw a line around features. Compose won’t do multi-node orchestration of deploys (I.e. update backends 1-3 sequentially, and revert the change on all of them if any fail to deploy).

It also doesn’t manage your configs; ie if you need to roll back, it won’t do that for you (though git will let you do that pretty easily).

I think Compose is great for the niches it serves; I have a lot of stuff that still runs on Compose because it doesn’t need any k8s stuff yet. I just don’t think it can be honestly called a k8s replacement. Compose offers equivalent features for some kinds of apps in certain situations, but k8s is a broader tool by far (for better or worse).

Re: We cut costs by 70% by moving from GCP and CockroachDB to Hetzner and PostgreSQL

#74

Post by lolinder » Tue, Apr 16, 2024, 12:26 AM UTC

everforward wrote: post #73

lolinder wrote: post #38

Earlier quoted context omitted.

With Docker Compose you can define volumes, versions, and configs can be volumes that point to a file that lives alongside your compose.yaml.

Sure, depending on how you want to draw a line around features. Compose won’t do multi-node orchestration of deploys (I.e. update backends 1-3 sequentially, and revert the change on all of them if any fail to deploy). It also doesn’t manage your configs; ie if you need to roll back, it won’t do that for you (though git will let you do that pretty easily). I think Compose is great for the niches it serves; I have a lo…

Agreed—people on here are only recommending compose because OP only has the single node, which places their app squarely within the realm of what compose is very good at.