Live data from Hacker News

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

blog.mikoto.io

21–30 of 74 posts

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

#21
As an SRE who’s moved between a few companies recently, I’ve noticed a trend towards simpler infrastructure options rather than k8s. Most places I interviewed at used AWS with just fleets of EC2s managed through ASG and instance refresh.

Deployments are no downtime. It’s pretty nice and if you want to run with docker on the host instances you can but you can also just install the application using systemd.

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

#22
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.

For me, the main benefit of Kubernetes is declarative deployments. You can have the entire deployment automated through this and GitHub actions, without much fiddling with the production environment manually. I know, it's overkill and I don't like it that much either, but it's the industry standard.

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.

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

#23
post #15

I should write a blog about how I saved the same amount in absolute terms by turning off the stuff i forgot is running in the cloud. Side note: the anime girls all over is kind strange. Like the header is giant cartoon tits? Why?

I use AI-generated anime girls for article covers because I'm a weeb and it makes the rather-thick wall of text slightly more bearable.

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

#24
The time investment here doesn’t really make sense to me. That 70% savings was actually only $33 a month.

Was it really worth spending that dev time and effort for such a small return rather than the product itself?

And yea now you get to manage your own cluster… thats an ongoing cost too, not free.

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

#26

Earlier quoted context omitted.

For me, the main benefit of Kubernetes is declarative deployments. You can have the entire deployment automated through this and GitHub actions, without much fiddling with the production environment manually. I know, it's overkill and I don't like it that much either, but it's the industry standard.

> but it's the industry standard. I strongly disagree with this statement. Even at the most bubbly of Silicon Valley events you will not see kubernetes for a smaller deployment be an industry standard. It’s ok to make architectural mistakes, or otherwise over engineer a thing. We all do it. Let’s not standardize it. And to your credit thank you for publishing this example as a learning opportunity to others.

I mean as in what the big (and small) clouds support. I haven't seen any clouds supporting Hashicorp Nomad or Docker Swarm!

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

#27
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.

For me, the main benefit of Kubernetes is declarative deployments. You can have the entire deployment automated through this and GitHub actions, without much fiddling with the production environment manually. I know, it's overkill and I don't like it that much either, but it's the industry standard.

Overkill is an understatement and “industry standard” is a misrepresentation. There are PLENTY of more appropriate options here, for this scale, without going off the beaten track. This is wanting to use the big kids’ tools when it doesn’t make sense to.

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

#28
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.

For me, the main benefit of Kubernetes is declarative deployments. You can have the entire deployment automated through this and GitHub actions, without much fiddling with the production environment manually. I know, it's overkill and I don't like it that much either, but it's the industry standard.

Use docker compose or ansible for this scenario.

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

#29

Earlier quoted context omitted.

For me, the main benefit of Kubernetes is declarative deployments. You can have the entire deployment automated through this and GitHub actions, without much fiddling with the production environment manually. I know, it's overkill and I don't like it that much either, but it's the industry standard.

> but it's the industry standard. I strongly disagree with this statement. Even at the most bubbly of Silicon Valley events you will not see kubernetes for a smaller deployment be an industry standard. It’s ok to make architectural mistakes, or otherwise over engineer a thing. We all do it. Let’s not standardize it. And to your credit thank you for publishing this example as a learning opportunity to others.

k3s is a teensy sqlite based orchestrator, something tons of devs run on their laptops for local dev. I think those are all single box clusters, why is it crazy to run it on a server but not a laptop?

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

#30
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.

For a single node cluster, just use minikube (or RKE2 if you have masochistic tendencies). And if everything runs on a single small vps, why even use postgres and not SQLite.
Post reply on HN