622 karma · joined September 6, 2021
GitHub: @juzhiyuan
This confused me because sometimes the title and link are mismatched
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/
P.S Apache APISIX supports using WASM, which means we could use Java, Golang, Python to implement plugins and run it in APISIX’s core.
I want to know, does "nginx -s reload" lead to trouble for your business? Someone said it's ok to do this because this action doesn't affect existing connections, but let's think about two cases:
1. NGINX doesn't know when the WebSocket connections will quit;
2. If using NGINX in K8s, should we do "nginx -s reload" when Pod changes?
P.S. The link should be https://apisix.apache.org
If you have any ideas or questions about Apache APISIX, kindly file an issue to submit here[1].
Also, there has a related issue: https://github.com/apache/apisix/issues/5966#issuecomment-10...
You could leave issues to GitHub apache/apisix repo :)