Joe Topjian

> So, downstream gobetweens will keep track on backends, performing discovery, that will be pulled by upstreams and merged into one big list of backends. Upstream gobetweens will be in...

@nickdoikov All good points. > Let`s assume that we have this feature, but all discoveries can and will respond asynchronous, Agreed. Multiple discoveries means distributed communication which means asynchronous which...

@nickdoikov What do you mean by "sub discovery" and "multi discovery"? I might have the same concepts in mind, but might be thinking of them in different names. > Also...

@yyyar It's a pretty clever solution :) I like that it's able to keep the current plugin architecture and retain backwards compatibility. Since one goal is to be able to...

@zacksiri > How would his work with multiple discoveries? i mean now the configuration difficulty for gobetween / lxd / node networking will be very difficult. Now we're talking cross-node...

> However I’m curious, isn’t setting up gobetween locally already like setting up a shared proxy device across all nodes? Yes, but one thing to keep in mind is that...

@yyyar I apologize for the late reply. I haven't been able to deploy gobetween in my infrastructure lately since the pending multi-backend support proves to be a requirement. This is...

@illarion Yes: https://github.com/yyyar/gobetween/issues/112

@hirikarate I'm not very familiar with Docker Swarm, but looking at your above diagram, it looks very similar to what I came up with here: https://github.com/yyyar/gobetween/issues/77. My idea was that...

@hirikarate > My propblem is , as I stated at the beginning of this topic, Gobetween is not domain-name-aware, so I cannot redirect requests to related internal micro services. Eg:...