3 ms·
Disclosure I work at Kong The comparison doesn’t fully translate because Envoy is a proxy, and Kong is a control platform that comes built on top of a proxy. W
by mikejulietbravo 8y ago
Disclosure I work at Kong
The comparison doesn’t fully translate because Envoy is a proxy, and Kong is a control platform that comes built on top of a proxy. We actually love envoy here, and think it’s a great product. The value that Kong brings is more up the information and abstraction stack versus just the core proxy we’re built on, which is rapidly becoming commoditized.
- navaati 8y agoHi. Not OP, but thanks for your great answers ! Does Kong compare more to Istio then (which as far as I understand is a control layer over Envoy), but less focused on K8s ?
- mikejulietbravo 8y agoKong would be more comparably to Istio, yes and we're big fans of it! We provide additional control capabilities on top of what Istio provides and can integrate with Istio for folks using it. Basically, if you're using Istio for a mesh, and you want to have that mesh also work with all your other non-mesh services, we help make that happen. You can also use Kong as an ingress controller for K8s or inject it as a sidecar proxy in K8s, which would give you very similar capabilities to using Envoy + Istio.
- mikejulietbravo 8y agoAlso, you are quite welcome!