you can build these without shared memory using standard distributed database techniques for serializability and fault tolerance. i dont think its a particularl

you can build these without shared memory using standard distributed database techniques for serializability and fault tolerance. i dont think its a particularly good idea. there's nothing great about running 'ps' and getting half a million entries. using the unix user/group model isn't great for managing resources. its not even that great to log in to start jobs. the only thing your gaining is familiarity. building better abstractions - kuberenetes is an example, although i certainly hope we dont keep being stuck there - is probably a better use of time