|
|
|
|
|
|
by kris-nova
1371 days ago
|
|
|
To be clear I see the "gRPC server" that listens over a unix domain socket being something more like pid 10-20. If there is a network "gRPC server" as well, I suspect it would be somewhere in the 20+ department. I don't anticipate exposes the actual pid 1 over a network. I'm not a monster. I suspect there will be be an init/jailer mechanism that manages bringing some of the basics online such a system logger and any kernel services (EG: ZFS) right away. One of the first "services" would be a d-bus alternative that is written in Rust and leverages gRPC. The main motivation behind gRPC is cloud, mTLS, and the support in rust. It comes with the ability to implement load balancing and connection error management/retry capabilities. I have week opinions on the technical detail as I don't suspect the network traffic will be very large. gRPC is more familiar for folks in cloud, as well as supports a large number of client languages for generating clients. |
|
|