4 ms·
Comments inline but I think the gist of what you're saying is: * containerization is good in general * k8s' binpacking is good for efficiency --- > Than nor
by alecbz 5y ago
Comments inline but I think the gist of what you're saying is:
* containerization is good in general
* k8s' binpacking is good for efficiency
---
> Than normal processes that are platform dependent.
Why/how is k8s more efficient? Do you just mean binpacking?
> I guess other platforms also solve this, but the concept of containers (and Docker streamlined it) was the first. Everyone followed later.
"We should use containers" is different than "we should use k8s".
> Compared to having heterogeneity, even in your local environment, let alone in a production system.
Sorry I meant "compared to what other systems" not "what's the alternative to cloud flexibility?"
> Agile. CI/CD.
Here again I guess you just mean via containerization in general?
- zekrioca 5y agoI didn’t say neither, but I know why they exist. Basically, I said these (containers, binpacking, load-balancing, proxying, name spacing, isolation, etc) are all realizations and solutions to problems that one needs to solve when autonomically managing any distributed system that is being shared among multiple distributed applications, each using their own deployment model. You don’t need to use k8s. But if you want scalability and manageability, you have to solve the same kind of problems it tries to solve, because ultimately resources aren’t infinite. Of course, this will always depend on the size of your (multiple) service(s).