Digital ocean has Kubernetes ffs.

It's all of five minutes to write a deployment yaml and ingress and have literally anything on the web for a handful of dollars a month.

I've written rust services doing 5k QPS on DO's cheapest kube setup.

It's not rocket science.

Serverless node buns with vite reacts are more complicated than this.

Ten lines of static, repeatable, versioned yaml config vs a web based click by click deploy installer with JavaScript build pipelines and magical well wishes that the pathing and vendor specific config are correct.

And don't tell me VPS FTP PHP or sshing into a box to special snowflake your own process runner are better than simple vanilla managed kube.

You can be live on the web from zero in 5 minutes with Digital Ocean kube, and that's counting their onboarding.

Litestream [1] is quick to set up and has point in time backup to the second.

- [1] https://litestream.io

“Guys, we need to postpone our beta launch! We need another week to implement a backup strategy with point in time recovery!”

You don’t need backups until you have customers.

Yes, and is super easy.

I do like this: cron to run the backup and then rsync to https://www.rsync.net, then an after script that check it was run and post to my telegram the analysis.

That is.

And also incredibly trivial to fix. Most VPS providers include their own backup services, and for the rest there's rsnapshot and some other cheaper VPS somewhere else to keep it "off site."

Too many have forgotten what it means to administrate a single system. You can do a lot with very simple tooling.

The better availability and scalability of “the cloud” always relied on so many things being done and maintained just right by just the right people that I don’t think it’s ever been broadly true.

You get such a large performance malus and increase in complexity right from the start with The Cloud that it’ starts at a serious deficit, and only eventually maybe overcomes that to be overall beneficial with the right workload, people, and processes. Most companies are lacking minimum two of those to justify “the cloud”.

And that’s without even considering the cost.

What I think it actually is, is a way for companies that can’t competently (I mean at an organizational/managerial level) maintain and adequately make-available computing resources, to pay someone else to do it. They’re so bad at that, that they’re willing to pay large costs in money, performance, and maybe uptime to get it.

Remember if you ever feel disappointed, the king of scale Google playstore updates stats once a day

I end up explaining this term to every junior developer that doesn't know it sooner or later, the same way I explain bike shedding to all PMs that don't know it... often sooner, rather than later.

It seems to really help if you can put a term to it.

Heh, I was gonna say cargo cult might mean something different in today’s programming landscape but then I thought about it for a second and it actually reinforces th meaning.

A devops coworker found my blog and asked me how I host it, is it Kubernetes. I told him it's a dedicated server and he seemed amazed. And this was just a blog. It's real

I've worked at a startup that could've trivially ran on a single VPS and kept things simple yet had a dedicated infra guy using a full k8s setup.

Because I think precisely the indie hacker community is not as keen to default to the big-tech stacks, because those are neither indie, nor hack-y :)