fabio VS gateway

After some research and testing, I landed on using Consul and Fabio as the demo infrastructure. Of course, there is a myriad of other options to accomplish this task, but because of the low configuration and ease of use, I was impressed with this pairing. Both projects are mature and well-supported, and very flexible--just because you can run them with low configuration, doesn't mean you have to. I wanted to keep this demo constrained, but the exercise did get me excited about exploring things further: circuit breakers, traffic splitting, and more complex service meshes.

Sniffing the SNI from the underlying TCP connection is the proper way to do this.

a couple examples I know of(only know go ones of the top of my head):

https://github.com/fabiolb/fabio/blob/master/proxy/tcp/tls_c...

HAProxy, Traefik, FabioLB, gobetween, and F5 BIG-IP also support native integrations with Consul for service discovery / service mesh.

Check out https://github.com/fabiolb/fabio instead of traefik, it's 100x simpler and "just works". Traefik... I don't like traefik. Fabio is as simpler than traefik in the same way that the hashistack is simpler than k8s.

I use Hashicorp Consul and Hashicorp Nomad for service discovery and task scheduling respectively, with wesher for my internal private management network that Consul, Nomad, etc run on to protect the management interfaces. Fabio bridges the gap between the wesher wireguard VPN and the rest of my home network.

How do you feel about using Fabio (https://github.com/fabiolb/fabio) - in addition to/or replacement for traefik?

Its a new thing to me. Will definitely try that out with https://github.com/dosco/graphjin and https://github.com/nautilus/gateway which are golang graphql servers.

It's interesting, but I do have some questions. Does it support being Apollo Gateway Federated? Can I federate DGraph with it? How does it differ from [Tyk's Graphql gateway](https://github.com/jensneuse/graphql-go-tools) or [Nautilus](https://github.com/nautilus/gateway) ?