3 ms·

All true, but you've got a few issues: - Flame still assumes you have a server somewhere- this is purely for elastic workloads. - Dynamically scaling horizont

All true, but you've got a few issues: - Flame still assumes you have a server somewhere- this is purely for elastic workloads. - Dynamically scaling horizontally is not something "linux" can do for you: It's a legitimately hard problem because of all the usual distributed systems difficulties. - Often, there are workloads that are only needed occasionally but also have very different resource needs than the rest of the system. Being forced to not only create a new version of your application, but additionally a bespoke server setup and dedicated VM/Container image for that case takes something that could be trivial in the Flame model, and makes it take hours even for someone experienced. Basically, you really should've read the article first.

sgarland 3y ago
> Dynamically scaling horizontally is not something "linux" can do for you It can, depending on your definition of horizontal, and whether you accept that tools like HAProxy fall under the realm of “Linux administration.” systemd can spawn N services from a single definition file, which can then register with the load balancer. A small shell script could monitor those service cgroups for basic metrics like memory or CPU utilization, and then command systemd to scale up/down. This is horizontal from the app’s perspective. I’m not suggesting the above is a great idea, and you’d probably be better off with container orchestration of some kind – but tbf, all that’s doing is encapsulating cgroups and monitoring consumption to command scaling.