For personal projects I have been considering the best way to address FFI boundaries between languages. This will become particularly important with wasm, where there is a memory/process boundary between modules. This article <https://hacks.mozilla.org/2019/11/announcing-the-bytecode-alliance/> (section "nanoprocesses) shows how the memory model might be modeled with dependencies.
Something that struck me is that there is no good way to define these boundaries. The current standard to use C for all FFI is performant but far from safe -- what if these boundaries could be generated safely and at high performance (albeit not C performance). If gRPC could generate code for FFI then it would allow interchanging services in a local running process or microservice almost trivially. With a sand-boxing architecture like wasm, the safety would not be sacrificed when making the code FFI vs microservice. IMO gRPC is almost perfectly positioned to take advantage of this flexibility. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/a2652d7a-e848-4bf0-8d2f-f4c71553e2fa%40googlegroups.com.
