41–50 of 64 posts
“envoy” is another popular option and they are building a gateway solution for API/inbound traffic https://github.com/envoyproxy/gateway
I'm using it, it feels great
I'm using it, it feels great
Earlier quoted context omitted.
the same benefit you get from most reverse proxies. If you dont need it, then nothing. If you do need it, it's critical. If you: - have more than 1 upstream service to hide behind your api.bigcorp.com name? - want to enforce standard authn/authz patterns across lots of teams/backend services? - want a standard approach to all the Quality of Service management? - want to have a well defined lifecycle for your APIs? -…
Hi, could you please share more about “the really useful stuff” part?
Earlier quoted context omitted.
Most of the time an "API Gateway" provides nothing. Usually this kind of service is just looking at the request path and maybe the Authorization header. In general it's just a useless hop in the TCP connection chain from the client to the server.
I feel “useless hop in TCP connection chain” is treated as a virtue in “modern architecture.” Somehow micro services and cloud native turned into that. So yeah, slow response times, wasted infrastructure and most work put into I/O and serialization/deserialization. I think we forgot what actual monoliths look like and just kept decomposing… I guess that is an appropriate term.
does anyone know the history of the project? I hadn't really heard of this until earlier this year.
The open source API Gateway project, APISIX, was open sourced and donated to Apache Software Foundation by API7.ai[1] in 2019, many people asked why not use Kong, AWS or other products? The main reason was Kong relies on PostgreSQL and AWS Gateway is vendor locked, now Kong has supported the DB less deployment mode, Apache APISIX also supports this way, this mode is easy to maintain with GitOps.
Here has some useful links IMO:
1. https://apisix.apache.org/blog/2021/08/25/why-apache-apisix-... 2. https://apisix.apache.org/blog/2021/06/28/why-we-need-apache... 3. https://api7.ai/blog/why-is-apache-apisix-the-best-api-gatew...
P.S Apache APISIX has one Slack channel under the Apache Software Foundation, it reaches to 1000+ members today! (All from organic)
[1] https://api7.ai/
For my use case, this would have to be incredibly awesome for it to justify self-hosting such a complex and critical system. My current go-to solutions are AWS API Gateway, Azure API Manager and Apigee.
I share your concern about managing solutions. I only know AWS API gateway but I can tell you the features it offers are very limited compare to Foss solutions
Earlier quoted context omitted.
Hi, could you please share more about “the really useful stuff” part?
I’m assuming he means things like third party auth connectors
“envoy” is another popular option and they are building a gateway solution for API/inbound traffic https://github.com/envoyproxy/gateway
Years ago we were going to write an extension to Envoy to decode our side channel session info so we could do without per-language client intelligence and additional service calls.
We didn't want to blow up production traffic - millions of dollars of transactions - because of stupid memory management and pointer blunders.