Hacker News new | past | comments | ask | show | jobs | submit login

Odd considering Kong is based on Nginx and this is built by Kong.



Kong the company is the author of Kong Gateway, and Kuma Mesh. Two different products for different use-cases.


Right, 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.


Envoy 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.


Looks like Envoy is the clear winner in the API gateway war.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: