I was reluctant to click on the link expecting another Java project, but it seems to be based on Go. Refreshing. Maybe I'll give it a try.
The core of apisix is based on Lua actually, but it supports using Java via RPC.
Apache Apisix: Open-Source API Gateway and API Management Platform
31–40 of 64 posts
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#32I was reluctant to click on the link expecting another Java project, but it seems to be based on Go. Refreshing. Maybe I'll give it a try.
It seems that you can develop based on Go as well https://github.com/apache/apisix-go-plugin-runner
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#33What is the advantage of using this compared to plain Nginx or Envoy? Is it just static vs. dynamic config for routing?
You can use APISIX API Gateway as a traffic entrance to process all business data, including dynamic routing, dynamic upstream, dynamic certificates, A/B testing, canary release, blue-green deployment, limit rate, defense against malicious attacks, metrics, monitoring alarms, service observability, service governance, etc.
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#34What is the main benefit to running a gateway? Auth should already be handled by the api and adding things like rate limiting, ip address filtering ,caching and so on are ridiculously trivial..
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? - want to have a portal that describes the APIs, how they work and facilitate users getting access to them?
API Gateways are a thing because web servers that started out being used as reverse proxies were not that easy to configure and just did way too much web server stuff. API gateways made this easier, and added a host of security measures to make it somewhat safer when presenting APIs to the internet.
Then API management came along as a first class concern for orgs who want others to use their APIs.
It's good to see some FOSS innovation in this domain, most of the real open source API gateways are a huge mess. Kong is great, but the really useful stuff is part of the paid enterprise platform.
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#35Anybody has any idea about how this compares to Kong (what I've been using for years)?
In my opinion, the two most important points;
1. Apache APISIX is a project of the Apache Software Foundation, while Kong is a project controlled by a commercial company (it is possible to change the license).
2. The Apache APISIX community is more active and vibrant
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#36does anyone know the history of the project? I hadn't really heard of this until earlier this year.
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#37Earlier quoted context omitted.
Nice, thanks for sharing. It seems like an improved Kong, using the good parts of it, like Nginx and Lua. It makes me want to use it instead of the usual Kong, in next project.
Lua doesn't make it easy to create your own plugins at all. Kong guys themselves tried to offer a good use experience for this but failed more than once.
Good point, and Apache APISIX maintainers are actively improving the Plugin Development Documentation to make developers easy to onboard.
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.
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#38Hey folks, here has one blog from APISIX’s initial authors, those points may help you understand APISIX better: https://api7.ai/blog/why-is-apache-apisix-the-best-api-gatew...
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#39What is the main benefit to running a gateway? Auth should already be handled by the api and adding things like rate limiting, ip address filtering ,caching and so on are ridiculously trivial..
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?
Re: Apache Apisix: Open-Source API Gateway and API Management Platform
#40What is the advantage of using this compared to plain Nginx or Envoy? Is it just static vs. dynamic config for routing?
Apache APISIX also has several security features to help reinforce API security. For instance:
1. It can dynamically manage lots of TLS certificates and do the TLS/SSL terminate or use mTLS to communicate with the upstream; 2. Plugins like ACL, IP Restriction, CSRF, and Referrer Restriction restrict API access in different dimensions.