I'm working under cli tool wich must communicate with another foreground always running processes. Tool will be used on windows|osx machines. I had a problem with the choice of architecture for it, here is my thoughts:
- single binary, spawn daemon process[es] on start, communicate with signals or via loopback network. There are could be lot of headache with daemonization (have no clue how to daemonize windows process), daemon status checks.
- multiple executable files. Drawback - not obvious how cli could find worker process(pid files? process name lookup?), probably deployment issues.
I will be grateful for any advice on the topic of my problem
