Live data from Hacker News

Kubernetes and back – Why I don't run distributed systems

davd.io

41–43 of 43 posts

Re: Kubernetes and back – Why I don't run distributed systems

#41
post #38
post #36

Earlier quoted context omitted.

What is point exactly of saying something "might" happen 100% of the time?

The point is, that if you want it to happen, you can do it with just minor effort.

and when your single server dies, it suddenly stops happening..

Re: Kubernetes and back – Why I don't run distributed systems

#42
post #38

Earlier quoted context omitted.

The point is, that if you want it to happen, you can do it with just minor effort.

and when your single server dies, it suddenly stops happening..

If my backend home server dies. I will rebuild it from spare parts right away. If one of frontend servers dies, nothing really happened. Ill spawn new one somewhere else (VPS, cheap dedibox, whatever).

Re: Kubernetes and back – Why I don't run distributed systems

#43

Why on earth did the author even believe he needed K8s to serve 500 concurrent users? You could do that on a couple basic web servers behind a load balancer 15+ years ago. Hell, you could probably run the whole app, including the database on a single server if you don't care about availability.

For me its about IaC, automatisation.

Building my app, deploying a container image and building a helm chart is not a lot of work if you have experience and the initial additional work is only happening once.

After that, you have your whole app definition in code, seting up a second or third env takes 5 minutes.

I really should write a blog article about my stack and the advantges of it (git, kubernetes, argocd, helm, ...)

Post reply on HN