I couldn't believe I hadn't heard of it before and shockingly it's
been in the linux kernel for >= a decade ??
https://en.wikipedia.org/wiki/Transparent_Inter-process_Communication
The feature set seems like everything you'd want in a "scalability
proto" (aka zmq/nanomsg(ng) et al) but already encapsulated in
a posix socket API:
The only downside(s) I seem to be finding are,
- not a lot of usage (mostly bc peeps don't know about it ??)
- using a more recent kernel is recommended and in some cases docs
might be out of date?
- see a deeper summary @ SO here,
Check this resource list,
-
the project home page:
-
kernel docs/src:
-
cpython support (which also has existed for ages..),
-
3rd party py libs (obvi all a bit old),
I couldn't believe I hadn't heard of it before and shockingly it's
been in the linux kernel for >= a decade ??
https://en.wikipedia.org/wiki/Transparent_Inter-process_Communication
The feature set seems like everything you'd want in a "scalability
proto" (aka zmq/nanomsg(ng) et al) but already encapsulated in
a posix socket API:
https://en.wikipedia.org/wiki/Transparent_Inter-process_Communication#Features
excellent with (dynamic) wireguard tunnelling if desiring
secure low-latency usage.
https://en.wikipedia.org/wiki/Transparent_Inter-process_Communication#Service_addressing
a combo of resiliency/load-balancing on multihomed systems.
The only downside(s) I seem to be finding are,
might be out of date?
Check this resource list,
the project home page:
kernel docs/src:
erlang 👀
cpython support (which also has existed for ages..),
3rd party py libs (obvi all a bit old),