A developer who wants to create a fabric embedded application would only need to provide a very thin “shim” component in golang, which could communicate with nearly any kind of local resource including a unix domain socket, or shared memory (through c-go, etc.). The entire fabric embedded application would not need to be built in golang, just an interface that integrates it with the Xgress framework (which will become a “virtual NIC” in fabric 2.0).
We could, in the future, provide some pre-built shims that make integrations with commonly used languages very straightforward.
Fabric embedded applications could certainly be supported directly in the NF console in the future. At this point, we just need some earlyvangelists to start working with these components. As usage increases, we’ll invest more into integrating support into the management console, etc.
For what it’s worth, the Ziti edge is a “fabric embedded” application. So we’re very much dog-fooding this ourselves.
@anantha Please feel free to reach out if you would like to discuss your use case in more detail. Would be happy to get on a call or provide support if it would be helpful.