Route is still present but underlying routetable isn't used about halibut HOT 5 CLOSED

No, but it is something I want to build at some stage.

from halibut.

We'll remove this in the next major

from halibut.

@droyad 👌
Is there actually an easy way to do this conceptually, without re-implementing the service on an in-between point?
For example have a lot of workers (cough azure functions for example) route the Halibut connection via a central point for all clients/servers to connect through.

from halibut.

@droyad We might be able to put some effort into this.
What line are you thinking of going with this? Would be nice to contribute in a way that's useful for everyone.

From our pov it'd be ideal to separate out all the work to create the invocations from the actual routing/client connection handling. This would allow a lot of vertical scaling options (dynamic workers a-la azure functions/lambda functions or even simply scaled VM's etc).

Ideally we'd even get the ability to get clients connecting to localized servers (EU, US, Asia) to improve client connectivity and our workers to connect to a central gateway that routes it to those localized gateways which then routes it to the appropriate client.

from halibut.

@droyad

As my colleague @janpieterz said before, we're very keen on having routing functionality implemented into Halibut for various reasons.

We've started work towards this and would love to have your feedback about simple changes we've made that could enable routing functionality. Our goal is to implement this in a way that would suit everyone so that we can contribute those changes back into Halibut.

POC can be found here: https://github.com/willemda/Halibut/tree/feature/routing/source (Run SampleClient, SampleProxyServer & SampleServer)

Changes can be summarized by this single file changes (HalibutRuntime.cs) :
willemda@018f2ce#diff-e9557d3eda420c227f8e7efdeac71162

• When sending a message, we make use of the routeTable dictionary to check if we need to route the message through another endpoint.
• When receiving a message, we check if the destination of the message matches the current endpoint, if not, we try and send this message over (can be routed again potentially). If yes, we process as usual

from halibut.