I love systemd. I use it extensively in production. The constraints handling (ex: service depends on database which depends on network) is great. You can have a

I love systemd. I use it extensively in production. The constraints handling (ex: service depends on database which depends on network) is great. You can have a systemd timer restart another timer that was suspended when the system load was too high, etc. Systemd is the best way I know to handle programs that can fail randomly, with complex dependencies. Just tweak the restart limits on the service. You can manage the whole set of dependencies. It can even be instructed to reboot the server. However, documentation could be better. For example, I have not been able to use yet the new feature allowing services to join existing namespaces not created by systemd (so not JoinsNamespaceOf=, but NetworkNamespacePath= ; cf otherwise https://cloudnull.io/2019/04/running-services-in-network-name-spaces-with-systemd/ https://cloudnull.io/2019/04/running-services-in-network-nam...) But systemd is still a bit new. Documentation and best practices will improve. EDIT: actual technical content get downvoted as usual, while opinion pieces about systemd being the antechrist fly.