Hi there,
I've got another question regarding tunnelers. For that, I quickly have to explain our setup:
We do have multiple processes(=services) communicating with each other via TCP - even on the same host. We're willing to rely on host access as a trust model, so unencrypted traffic on localhost is no issue. However, there are also other processes/services on different hosts that local services need to talk to.
Naturally, I thought we had two options:
- Either integrate the SDK right into the processes
- Install a tunneler on each host
However, both options have some drawbacks for us:
- SDK - Network Resilience: Once the connection to the controller is lost due to some network outages, even processes on the same host won't be able to communicate with each other. In that case, we would have to spin up another local controller for the time being.
- Tunnelers - No API: The tunnelers have to be installed separately (we plan to support Windows & macOS as well). Furthermore, they have to be configured by the user manually since they don't provide any API
Ideally, there would be some forward- and reverse proxy with an API for communication with services on other hosts. As far as I can see, we would have to write such a proxy on our own, right? There is something like that for Kubernetes / Linux as far as I can see, however, not for Windows/macOS.
Thanks!