4 ms·
They do have a comparisons section in their docs, but it's just marketing fluff. https://kuma.io/docs/0.1.1/#kuma-vs-xyz https://kuma.io/docs/0.1.1/#kuma-vs-xy
by sciurus 7y ago
They do have a comparisons section in their docs, but it's just marketing fluff.
https://kuma.io/docs/0.1.1/#kuma-vs-xyz https://kuma.io/docs/0.1.1/#kuma-vs-xyz
If nothing else, looks like they're both built around Envoy.
- meddlepal 7y agoOdd considering Kong is based on Nginx and this is built by Kong.
- fosk 7y agoKong the company is the author of Kong Gateway, and Kuma Mesh. Two different products for different use-cases.
- meddlepal 7y agoRight, I understand that, but I was just commenting that it is odd they didn't built it on top of Nginx. I would have expected that rather than switching to Envoy.
- carlallison 7y agoLooks like Envoy is the clear winner in the API gateway war.
- fosk 7y agoEnvoy has a proven track record in Mesh deployments, whereas in NGINX those primitives have to be built from scratch. On the other end, NGINX has proven track record as an Ingress Gateway and therefore it is the natural technology as an APIM solution.