Hi Kong Team,
Currently, LB to targets in an upstream employs a weighted-RR LB pattern.
It would be very beneficial for certain deployment configurations (particularly multi-dc) if we could support load balancing based on data-center or (preferably) healthcheck ping latency.
What I suggest: Is to add a new loadbalancing option to Kong for a node to locally cache the most recent healthcheck ping response times for all targets in an upstream, and route exclusively to the target with the lowest response times. This would allow users to greatly customize their routing, as it would largely be based on the frequency and concurrency of healthchecks.
I’d love some guidance from the Kong team on where to start looking to add some of this functionality!