3 ms·

> route by query string, configure weighted load balancing, work with TLS, deal with methods, etc - let alone other protocols than HTTP Except for weighted loa

> route by query string, configure weighted load balancing, work with TLS, deal with methods, etc - let alone other protocols than HTTP Except for weighted load balancing*, these are all things NGINX does, which Kong is built on via OpenResty, right? What makes Kong different? (Trying to be open to explore even though I was disappointed when Insomnia users got locked out of their data unless they signed up for an account when they updated what was marketed as an open source project) * Which I think NGINX Plus, a competitor, probably has, and they have an Ingress controller for Kubernetes that would likely get updated to use the Gateway API soon.

mflendrich 3y ago
> What makes Kong different? I am specifically talking just about OSS functionality in the Kong Ingress Controller. It can assign weights to service backends. And, FWIW, Insomnia 8.3 defaults to local projects (again) https://konghq.com/blog/product-releases/insomnia-8-3 https://konghq.com/blog/product-releases/insomnia-8-3 Gateway API is a broad community standard governed by SIG Network - fingers crossed for various other implementations (including mesh) working their way to GA implementation-wise - this will make the standard stronger and the community more vibrant.