One thing that annoys me is that when "directing" other programs, you need to write tests that check if each program is alive and kicking. If you for example is

One thing that annoys me is that when "directing" other programs, you need to write tests that check if each program is alive and kicking. If you for example is checking a http server, you need a http client to test it. And the most frustrating part is that you don't know when the program is ready to do whatever it's supposed to do, so you have to constantly poll until it answers, but then when you disconnect it might have some warmup/warmdown mechanism, so you can't put it to use right away, you have to do manually testing - then set a timeout with a good margin. Then when you "director" worker crashes (and restarted by another "init" service) those children are still alive, so when you try to start another instance it will complain about the port being used, so the "director" worker also have to check for existing orphans. .. It's sometimes easier to just rewrite the program yourself so it becomes a port of you "monolith". I like the unix philosophy and micro-services. But I feel it can be better...