in which case I think you can use the service of your choice. They both do a good job here.
However, if the service is to be monitored in the sense of a daemon, systemd has advantages here:
systemd starts the service and also monitors whether it is still running. If desired, systemd can also restart the service automatically after a crash.
Dependencies at system startup are detected and, if necessary, the start of a service is written to a pipe until the calling service is ready. This speeds up the start enormously, because almost everything can be started in parallel. Everything is logged in the log.
With a little practice, service and timer units are quickly created and very flexible.
In almost all distributions, systemd is now standard. Therefore, a systemd service can be run on many installations without additional dependencies.
It is just a new and almost everywhere available method to start the system and services on Linux machines.