3 ms·

I think I need more than 5 quick bullet points for the “why”. > Resource efficiency What does this mean? More efficient than what? > Seamless scalability on

by alecbz 5y ago

I think I need more than 5 quick bullet points for the “why”. > Resource efficiency What does this mean? More efficient than what? > Seamless scalability on containers or nodes Not sure what “on containers” means. “On nodes”, sure. Do other platforms not solve this as easily? (Running multiple workloads per host) > Built-in scheduler I guess same question as above, there aren’t other solutions where you give something a fleet of hosts and it runs things on them? > Cloud flexibility Again compared to what I guess? > Pushing to apply engineering best practices Such as?

zekrioca 5y ago
> What does this mean? More efficient than what? Than normal processes that are platform dependent. > Not sure what “on containers” means. “On nodes”, sure. Do other platforms not solve this as easily? (Running multiple workloads per host) On containers means your application is packaged to be used as a consumable service, that is in turn used to compose a more complex workflow service that solves a ‘real’ problem. I guess other platforms also solve this, but the concept of containers (and Docker streamlined it) was the first. Everyone followed later. > I guess same question as above, there aren’t other solutions where you give something a fleet of hosts and it runs things on them? There are years of bin-packing research (think operations research from 50’s). But none of them came with the integration that something like K8S brought. Mesos is another example, but comercial support is slowly killing it. > Again compared to what I guess? Compared to having heterogeneity, even in your local environment, let alone in a production system. > Such as? Agile. CI/CD.
- 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 ago
    I 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).

by alecbz 5y ago

zekrioca 5y ago

> What does this mean? More efficient than what? Than normal processes that are platform dependent. > Not sure what “on containers” means. “On nodes”, sure. Do other platforms not solve this as easily? (Running multiple workloads per host) On containers means your application is packaged to be used as a consumable service, that is in turn used to compose a more complex workflow service that solves a ‘real’ problem. I guess other platforms also solve this, but the concept of containers (and Docker streamlined it) was the first. Everyone followed later. > I guess same question as above, there aren’t other solutions where you give something a fleet of hosts and it runs things on them? There are years of bin-packing research (think operations research from 50’s). But none of them came with the integration that something like K8S brought. Mesos is another example, but comercial support is slowly killing it. > Again compared to what I guess? Compared to having heterogeneity, even in your local environment, let alone in a production system. > Such as? Agile. CI/CD.

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 ago
  I 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).