- Well is your setup for Kong multi DC? If so you need something infront of Kong to toggle DNS to go between the datacenters? If using vendor products an F5 GTM generally does that DNS manipulation(never worked anywhere else so maybe there is an opensource version of something that messes with DNS). Then you have a Device on each IP that GTM points to serving as a loadbalancer performing healthcehcks against Kong to see if its running and sending traffic to it. Although maybe Kong can be the IP the GTM resolves to and somehow the GTM acknowledges is health automatically?
If you just want a list of LB’s in general there are plenty, HA Proxy, Nginx, Envoy to name a few.
- I don’t think the performance difference is enough to matter really. Is the Docker container going to be running on bare metal then? Or just another VM running Docker lol? If so I would think the OG VM would be best. Otherwise you have tech stack inception going on(running Docker container on a VM). If I had my way I would be running Kong on some bare metal beefy physical servers and enjoying that direct cpu and mem to the veins.