← Back to context

Comment by layer8

14 days ago

The OP doesn’t serialize. My proposal would still serialize as with RPC, but instead of passing the data over a socket, just pass the data as a binary blob over a regular function call.

The main thing on my mind is that the build system would become more bespoke when doing it that way, compared to running a few processes that interact with each other.

The overhead of socket read+write is typically much less than the serialization overhead, although both can be optimized to the point of irrelevance for many applications.

It's also interesting because it ends up looking like a microservices architecture, except all on one machine (even all in one process tree).