3 ms·

So basically, ignore 1/2 of the reasonable problems that are solved in the first article and then look, no need to learn anything!!! As someone whom can setup

So basically, ignore 1/2 of the reasonable problems that are solved in the first article and then look, no need to learn anything!!! As someone whom can setup and run a kubernetes cluster in my sleep, I can tell you that it is a superb production ready platform that solves many real world problems. That in mind, kubernetes has constraints also, like running networked elixer containers is possible, but not ideal from elixer's perspective. Dealing with big data takes extra consideration. etc. etc. All said, if you have an interest in DevOps/Ops/SysAdmin type technologies, learning Kubernetes is a fine way to spend your time. Once you have a few patterns under your belt, you are going to run way faster at moving your stack to production for real users to start using, and that has value. I think the initial author (not this article, the other one) was just pointing out that you can indeed run kubernetes pretty cheap, and that is useful information and good introduction. This article is clickbait designed to mooch off of the others success.

emodendroket 8y ago
> So basically, ignore 1/2 of the reasonable problems that are solved in the first article and then look, no need to learn anything!!! I think the point is... do you actually have those problems? A lot of people jump immediately to worrying about having thousands of requests per second when it doesn't make any sense.
- whydoineedthis 8y ago
  Sharing code and getting run on other collaborators workstations? Yes, that's a very real developer problem. Deploying without downtime? Yep, it's nice to have because your favorite customer will have been testing that site in the exact 2 minutes of downtime which you deploy it ....believe me, murphy's law rules here. Staging and Production environments that are the same, so I don't have surprises from local development to production release? Yep, another real problem that will slow momentum of development. I suppose if you are developing a personal project of garbage that no one will ever see, than these problems don't exist. But if you are actually developing a product, these problems exist.

emodendroket 8y ago

> So basically, ignore 1/2 of the reasonable problems that are solved in the first article and then look, no need to learn anything!!! I think the point is... do you actually have those problems? A lot of people jump immediately to worrying about having thousands of requests per second when it doesn't make any sense.

whydoineedthis 8y ago
Sharing code and getting run on other collaborators workstations? Yes, that's a very real developer problem. Deploying without downtime? Yep, it's nice to have because your favorite customer will have been testing that site in the exact 2 minutes of downtime which you deploy it ....believe me, murphy's law rules here. Staging and Production environments that are the same, so I don't have surprises from local development to production release? Yep, another real problem that will slow momentum of development. I suppose if you are developing a personal project of garbage that no one will ever see, than these problems don't exist. But if you are actually developing a product, these problems exist.