Service manager and dependencies

[olanod]

Most useful OSs "do stuff" aside from the one application the user decided to execute, often in the form of background applications/daemons/services. These services don't run all at the same time, they pop on and off existence based on data becoming available, another service "waking them up" or any other condition, it's all a symphony of data flow all over the place ;P
To make this possible there's usually a master program, our service manager, coordinating how things on the system are run and making sure the conditions that each service specified for its execution are met... So yeah a service manager/orchestrator would be cool 😅

An idea I'd like to play with, I had started with the draft of a project that creates wasm pipelines that uses a directed graph to define how data flows between dependent wasi apps reading data through stdin and spitting stuff to stdout inspired by how gstreamer works, now that I started learn your employer's framework substrate I've been caught in the idea of re-purposing it as something more general that could be used as the off-chain worker engine or a general purpose service manager. I wanted for example have a source that produces data by executing a wasm bin on a specified interval, the data then passes to a bin that was already running and waiting for data(and might need to be respawn if it fails) or a oneshot bin ... it will start to look a lot like a system manager right? 🤔 anyway, much excitement and little code but what better way to test the idea than with a WASM based OS!

[tomaka]

Well, the "service manager" is basically the kernel's scheduler.