Live data from Hacker News

“You don't need this overengineered goo for your project.”

twitter.com

11–20 of 107 posts

Re: “You don't need this overengineered goo for your project.”

#11
post #5

‪That’s not an architecture diagram though, so it doesn’t represent the complexity at all. I’m sure a troubleshooting map for bare linux server wouldn’t be less complicated than that.‬

> I’m sure a troubleshooting map for bare linux server wouldn’t be less complicated than that.‬

Except your k8s runs on a Linux server, so this is just an addition. (Unless you're using a fully managed k8s cloud offering, but then you have an even bigger toubleshooting flowchart to navigate the provider's management interface: at least that's my experience with GKE, maybe Amazon and others are better)

Re: “You don't need this overengineered goo for your project.”

#12
post #5

‪That’s not an architecture diagram though, so it doesn’t represent the complexity at all. I’m sure a troubleshooting map for bare linux server wouldn’t be less complicated than that.‬

When I first saw it K8S reminded me a lot of systemd. I wouldn't be surprised if over the next few years each grow the features of the other.

Re: “You don't need this overengineered goo for your project.”

#13
post #2

recently facing the dilemma of choosing between k8s vs something more basic. Features that seemed to be advocating for k8s were not server provisionning, but instead : log management, easy setup of blue/green & canary deployment, not having to restart a vm upon new code deployment, etc... How would you do those things as easily with other techs ?

aws elastic beanstalk

all what a modern web app needs out of the box with 1 day to learn instead of years... and the best? you don't have to modify your code to work on it, ie environment and code are separate.

Re: “You don't need this overengineered goo for your project.”

#15
post #14

> StackOverflow runs on a couple of servers. K8s can as well. The difference is a bunch of servers running k8s or a bunch of servers running custom code to duplicate parts of k8s.

Or a couple of servers running IIS with a handful of web apps, maybe a reverse proxy.

Re: “You don't need this overengineered goo for your project.”

#18
post #2

recently facing the dilemma of choosing between k8s vs something more basic. Features that seemed to be advocating for k8s were not server provisionning, but instead : log management, easy setup of blue/green & canary deployment, not having to restart a vm upon new code deployment, etc... How would you do those things as easily with other techs ?

aws elastic beanstalk all what a modern web app needs out of the box with 1 day to learn instead of years... and the best? you don't have to modify your code to work on it, ie environment and code are separate.

And if they don't like your politics, they simply pull the plug.

Re: “You don't need this overengineered goo for your project.”

#19
post #16

> StackOverflow runs on a couple of servers. Does it?

Yes it does: https://stackexchange.com/performance Pretty impressive I think.

No it doesn’t. From your link:

• 9 web servers

• 4 SQL servers

• 2 Redis servers

• 3 tag engine servers

• 3 Elasticsearch servers

• 2 HAProxy servers

That comes to 23. I know “a couple” is sometimes used to mean more than two, but… not that much more than two.

“A couple” is just flat-out wrong; I’d guess that he’s misinterpreting ancient figures, taking the figures from no later than about 2013 about how many web servers (ignoring other types, which are presently more than half) they needed to cope with the load (ignoring the lots more servers that they have for headroom, redundancy and future-readiness).

Post reply on HN