Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to seperate the popularity from other things.
This is just a picture of this link from July 13, 2017
A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:
- security (TLS for service to service authentication)
- intelligent traffic management (proxy, deployed as a sidecar to the relevant service)
- visibility (monitoring and tracing for troubleshooting and debugging)
Lyft's Istio or Twitter's Linkerd are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio, large companies implemented the same functionality using fat client libraries.
In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
More Articles:
