Live data from Hacker News

You might not need Kubernetes

blog.jessfraz.com

51–60 of 319 posts

Re: You might not need Kubernetes

#51

Earlier quoted context omitted.

Does hacker news really run on one server? What if server goes down? I've always though high availability was the more important reason for multiple servers, rather than performance. Even if you have only two paying customers, they are probably paying for the right to hit your website / service 24/7.

Has hacker news ever gone down? I cant remember it ever going dkwnt but I assume it has to have at some point.

I've seen it happen at least once in the few years that I've been on Hacker News, see https://news.ycombinator.com/item?id=17228704

Re: You might not need Kubernetes

#52
post #13

Depends on the scale. If I only have 10 containers to manage I'd throw them on a m4 and let it be. Benefit of using k8s kicks in when your use case gets complicated.

What's m4?

Probably the AWS m4 instance type, meant for general purpose workloads (and replaced with the m5 instance type about a year ago).

https://aws.amazon.com/ec2/instance-types/m5/

Re: You might not need Kubernetes

#53
post #13

Depends on the scale. If I only have 10 containers to manage I'd throw them on a m4 and let it be. Benefit of using k8s kicks in when your use case gets complicated.

What's m4?

GP probably references an AWS EC2 machine type: https://aws.amazon.com/fr/ec2/instance-types/

Re: You might not need Kubernetes

#55

Some day I would like a powwow with all you hackers about whether 99% of apps need more than a $5 droplet from Digital Ocean, set up the old-fashioned way, LAMP --- though feel free to switch out the letters: BSD instead of Linux, Nginx instead of Apache, PostgreSQL instead of MySQL, Ruby or Python instead of PHP. I manage dozens of apps for thousands of users. The apps are all on one server, its load average around…

Does hacker news really run on one server? What if server goes down? I've always though high availability was the more important reason for multiple servers, rather than performance. Even if you have only two paying customers, they are probably paying for the right to hit your website / service 24/7.

An interesting case study of an app at scale is Stack Overflow. Rather more than one server, but rather less than you might expect.

Edit: fixed url

https://nickcraver.com/blog/2013/11/22/what-it-takes-to-run-...

Re: You might not need Kubernetes

#56

Some day I would like a powwow with all you hackers about whether 99% of apps need more than a $5 droplet from Digital Ocean, set up the old-fashioned way, LAMP --- though feel free to switch out the letters: BSD instead of Linux, Nginx instead of Apache, PostgreSQL instead of MySQL, Ruby or Python instead of PHP. I manage dozens of apps for thousands of users. The apps are all on one server, its load average around…

For reference, this runs on a $5 AWS instance:

https://hnprofile.com/

The database is $600 per month, but that data runs five different websites (and it's a few hundred Gb of data).

EDIT: for those mentioning the 502 gateway error, it does auto scales - Now it's costing more per month, at least temporarily.

Re: You might not need Kubernetes

#57

Some day I would like a powwow with all you hackers about whether 99% of apps need more than a $5 droplet from Digital Ocean, set up the old-fashioned way, LAMP --- though feel free to switch out the letters: BSD instead of Linux, Nginx instead of Apache, PostgreSQL instead of MySQL, Ruby or Python instead of PHP. I manage dozens of apps for thousands of users. The apps are all on one server, its load average around…

FreeBSD, Apache, Python - the FAP stack

Ok. I'll see myself out.

Re: You might not need Kubernetes

#58
post #13

Depends on the scale. If I only have 10 containers to manage I'd throw them on a m4 and let it be. Benefit of using k8s kicks in when your use case gets complicated.

Perhaps three parallel m4's distributed across availability zones with identical sets of containers deployed to them, but yes.

Re: You might not need Kubernetes

#59

Some day I would like a powwow with all you hackers about whether 99% of apps need more than a $5 droplet from Digital Ocean, set up the old-fashioned way, LAMP --- though feel free to switch out the letters: BSD instead of Linux, Nginx instead of Apache, PostgreSQL instead of MySQL, Ruby or Python instead of PHP. I manage dozens of apps for thousands of users. The apps are all on one server, its load average around…

Not everyone uses K8s for webapps. You would be surprised at the level of enterprise penetration of K8s. Those enterprises do boring stuff like datawarehousing etc.

Re: You might not need Kubernetes

#60
post #11

"Anyways, the point I am trying to make is you should use whatever is the easiest thing for your use case and not just what is popular on the internet. " This is good advice in theory but in the real employment world you are killing your own career that way. At some point you get marked as "dinosaur" that hasn't "kept up". Much better to jump on the latest tech trend.

I get the sentiment here, but I don't think it's strictly true. The way I look at new technology is that I need to know enough about it to either discount it, or choose to use it. So long as I know what I'm talking about when I tell a prospective employer that I advise not using technology X, then they typically understand that I have the knowledge to make that decision.

So your advise should be, learn about the latest tech trend, try it out, and then have an informed opinion.

Post reply on HN