3 ms·
You will definitely add complexity if you want to run multiple app instances per node. I do not view that as particularly compelling for any runtime that suppor
by kasey_junk 4y ago
You will definitely add complexity if you want to run multiple app instances per node. I do not view that as particularly compelling for any runtime that supports concurrency out of the box in a virtualization environment.
As for health probes, I worked with load balancers in the late 90s that could use endpoint health checks so I’m not sure what you mean.
- pammf 4y agoI think it’s compelling from a scalability perspective given that deploying one OS for each app instance you want is quite wasteful and increase entropy: deploying from a single image doesn’t guarantee the os won’t change over time, and if you have 100 instances, keeping all of them consistent will require solutions that will inherently increase the overall complexity, which is the main argument against k8s. Regarding the endpoint health probes, I agree that’s possible if you have an app with a call that’s lightweight and representative enough to be used for that. But again, we are already deviating from the “pretty simple” solution here as well. And we didn’t even start talking about how to make the Load Balancer highly available… That said. I agree that the solution you’ve mentioned is a feasible one, I just don’t think that it’s way simpler than k8s if you truly have more demanding scalability and availability requirements.