Yes, it seems linkerd borrowed much of routing table from finagle:
https://linkerd.io/doc/dtabs/ <
https://linkerd.io/doc/dtabs/>
The other component that comes into play is what they call namerd, which provides name
resolution through external registries.
But AFAIK, APIMan already has support for registries like consul & zookeeper?
Regards, Heiko
On 31 May 2016, at 15:26, Marc Savy <marc.savy(a)redhat.com>
wrote:
Presently we don't have any such functionality, but I don't see why we
couldn't consider adding something like that. The underlying model may be flexible
enough (hard to say without trying, though).
I'd definitely like to investigate this at some point, though, as it'd
potentially be a valuable thing to support.
On 31 May 2016 at 12:49, Heiko Braun <ike.braun(a)googlemail.com
<mailto:ike.braun@googlemail.com>> wrote:
I was looking linkerd [1] the other day one feature caught my attention: the RPC routing
capabilities [2] (i.e. http, or thrift). I was wondering if a similar concept exists in
APIMan that allows for redirection of HTTP invocations and dynamic changes to the routing
tables?
Regards, Heiko
[1]
https://linkerd.io/ <
https://linkerd.io/>
[2]
https://blog.buoyant.io/2016/05/04/real-world-microservices-when-services...
<
https://blog.buoyant.io/2016/05/04/real-world-microservices-when-services...
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org <mailto:Apiman-user@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/apiman-user
<
https://lists.jboss.org/mailman/listinfo/apiman-user>