11–20 of 74 posts
I predict hard times for GCP as they will get squeezed by Amazon and Azure, plus the kind of belt-tightening we see here.
Not really. You didn't factor in the time it takes to manage k3s yourself versus GKE which is managed.
Probably. But it was only a single command to get up a k3s node - not much difference in effort for a relatively low-workload, low-critical service.
The point is that it's not really a fair comparison.
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.
Side note: the anime girls all over is kind strange. Like the header is giant cartoon tits? Why?
I predict hard times for GCP as they will get squeezed by Amazon and Azure, plus the kind of belt-tightening we see here.
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.
Fwiw I’ve deployed services that could handle 30-50k rps on 1vcpu and 1gb ram. Like a couple bucks a month. It used ssd storage and only hit a main rdbms when there was a cache miss.
When I hear stories like this I’m reminded of how dumb and inefficient most organizations are. My colleagues would over engineer stuff so much and then leave a huge bill and mess behind. The primary reason was so their clueless eng manager would consider promoting them.
Not really. You didn't factor in the time it takes to manage k3s yourself versus GKE which is managed.
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.
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.
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.