Live data from Hacker News

Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative

solo.io

1–10 of 16 posts

Re: Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative

#4

Why not just use Istio and Knative? Also Project contour can do the same as an api Gateway. What's the difference?

Can Contour actually do the same? For me, the main benefit of an API gateway is being able to specify an internal service to handle authn/authz. With Envoy that's done via a filter, iirc. Can you set that Envoy specific config with Contour?

Re: Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative

#5

Why not just use Istio and Knative? Also Project contour can do the same as an api Gateway. What's the difference?

Can Contour actually do the same? For me, the main benefit of an API gateway is being able to specify an internal service to handle authn/authz. With Envoy that's done via a filter, iirc. Can you set that Envoy specific config with Contour?

you can't. See GH issue: https://github.com/projectcontour/contour/issues/432

Re: Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative

#6

Why not just use Istio and Knative? Also Project contour can do the same as an api Gateway. What's the difference?

Istio is fairly resource intensive in my limited use. Contour is a bit simpler to configure and use with overlap.

Gloo has lots of other features, like WAF and Webassembly hooks for request flow.

Re: Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative

#7

Why not just use Istio and Knative? Also Project contour can do the same as an api Gateway. What's the difference?

Contour is not an API Gateway.

Disclaimer: I work for Solo.io

An API Gateway can do sophisticated edge security challenges (OIDC, Authz based on OPA, web app firewalling/WAF, etc) as well as things like message transformation, swagger/grpc detection, exposing APIs for self-service signup through a portal, etc. Gloo does all these things.

I've written in depth about this as well, specifically in terms of things like contour, Istio ingress gateway, consul's service mesh gateway, etc, etc

https://blog.christianposta.com/microservices/do-i-need-an-a...

Gloo resources: https://docs.solo.io/gloo/latest/guides/dev_portal/ https://docs.solo.io/gloo/latest/guides/security/waf/ https://docs.solo.io/gloo/latest/guides/security/auth/oauth/... https://docs.solo.io/gloo/latest/guides/security/opa/ https://docs.solo.io/gloo/latest/installation/advanced_confi... https://docs.solo.io/gloo/latest/guides/traffic_management/r...

Re: Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative

#9

Why not just use Istio and Knative? Also Project contour can do the same as an api Gateway. What's the difference?

Contour is not an API Gateway. Disclaimer: I work for Solo.io An API Gateway can do sophisticated edge security challenges (OIDC, Authz based on OPA, web app firewalling/WAF, etc) as well as things like message transformation, swagger/grpc detection, exposing APIs for self-service signup through a portal, etc. Gloo does all these things. I've written in depth about this as well, specifically in terms of things like c…

Thanks for the detailed response. In that regard, it is like Kong. What is the difference between Kong vs Gloo? Kong is based on nginx which is rock solid.

Re: Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative

#10

Anyone used Gloo and have any experience with it they can share? I've used Ambassador a bunch and they are pretty comparable, but curious what others think.

We have a list of our end users and customers listed here along with links to their talks and blogs about their experience with gloo https://www.solo.io/customers/
Post reply on HN