I like it better than wrangling init.d scripts, especially once you get a bunch of complex inter-dependencies in there. Usually you don't co-locate that stuff on a single server instance anymore (because you'd just handle orchestration via containers, e.g., Docker/Kubernetes), but 7 or 8 years ago, it was handy for spinning up stuff like WildFly/JBOSS in a custom systemd script to say, for example, "this service depends on the network, MySQL/MariaDB, and Samba." Again, pretty much irrelevant with single-purpose containers and better orchestration.
Apparently systemd has it's own container runtime as well in systemd-nspawn, which supports most container formats. Isn't an orchestration system though obviously. Not sure why Kubernetes doesn't support it as a backend.
I like it better than wrangling init.d scripts, especially once you get a bunch of complex inter-dependencies in there. Usually you don't co-locate that stuff on a single server instance anymore (because you'd just handle orchestration via containers, e.g., Docker/Kubernetes), but 7 or 8 years ago, it was handy for spinning up stuff like WildFly/JBOSS in a custom systemd script to say, for example, "this service depends on the network, MySQL/MariaDB, and Samba." Again, pretty much irrelevant with single-purpose containers and better orchestration.
Apparently systemd has it's own container runtime as well in systemd-nspawn, which supports most container formats. Isn't an orchestration system though obviously. Not sure why Kubernetes doesn't support it as a backend.