0.43.0 of grpc-over-datachannels is out. Two headline
features: a host/plugin model that lets one public endpoint
serve out-of-process plugins (a community request, issue
2), and unified packet-loss instrumentation that follows a
call across the SCTP, TCP, and HTTP/2 legs of its path.
One endpoint, many plugin processes
The request was simple to state: expose one grpc-dc
endpoint, and let independent processes register services
on it at runtime, without recompiling the host. 0.43.0
builds that from pieces the runtimes already had:
IPC transports. The Rust, JS, and Go runtimes speak one length-prefixed framing over stdio and Unix domain sockets, so a plugin is just a grpc-dc server whose transport is a pipe instead of a DataChannel.
Runtime registration. Servers can register and unregister services after serve() starts, in all three runtimes β a plugin connecting is a registration, a plugin exiting is an unregistration.
Interceptor chains.β¦