mirror of
https://gitee.com/iresty/apisix.git
synced 2024-12-05 05:27:35 +08:00
288 lines
23 KiB
Markdown
288 lines
23 KiB
Markdown
<!--
|
||
#
|
||
# Licensed to the Apache Software Foundation (ASF) under one or more
|
||
# contributor license agreements. See the NOTICE file distributed with
|
||
# this work for additional information regarding copyright ownership.
|
||
# The ASF licenses this file to You under the Apache License, Version 2.0
|
||
# (the "License"); you may not use this file except in compliance with
|
||
# the License. You may obtain a copy of the License at
|
||
#
|
||
# http://www.apache.org/licenses/LICENSE-2.0
|
||
#
|
||
# Unless required by applicable law or agreed to in writing, software
|
||
# distributed under the License is distributed on an "AS IS" BASIS,
|
||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||
# See the License for the specific language governing permissions and
|
||
# limitations under the License.
|
||
#
|
||
-->
|
||
|
||
# Apache APISIX
|
||
|
||
<img src="https://svn.apache.org/repos/asf/comdev/project-logos/originals/apisix.svg" alt="APISIX logo" height="150px" align="right" />
|
||
|
||
[](https://github.com/apache/apisix/actions)
|
||
[](https://github.com/apache/apisix/blob/master/LICENSE)
|
||
[](https://github.com/apache/apisix/graphs/commit-activity)
|
||
[](http://isitmaintained.com/project/apache/apisix "Average time to resolve an issue")
|
||
[](http://isitmaintained.com/project/apache/apisix "Percentage of issues still open")
|
||
|
||
**Apache APISIX** is a dynamic, real-time, high-performance API gateway.
|
||
|
||
APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more.
|
||
|
||
You can use Apache APISIX to handle traditional north-south traffic,
|
||
as well as east-west traffic between services.
|
||
It can also be used as a [k8s ingress controller](https://github.com/apache/apisix-ingress-controller).
|
||
|
||
The technical architecture of Apache APISIX:
|
||
|
||
|
||
|
||
## Community
|
||
|
||
- Mailing List: Mail to dev-subscribe@apisix.apache.org, follow the reply to subscribe to the mailing list.
|
||
- QQ Group - 781365357
|
||
- Slack Workspace - Please [subscribe the mailing list](https://apisix.apache.org/docs/general/subscribe-guide) then ask for invitation link
|
||
-  - follow and interact with us using hashtag `#ApacheAPISIX`
|
||
- [bilibili video](https://space.bilibili.com/551921247)
|
||
- **Good first issues**:
|
||
- [Apache APISIX®](https://github.com/apache/apisix/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
|
||
- [Apache APISIX® Ingress Controller](https://github.com/apache/apisix-ingress-controller/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
|
||
- [Apache APISIX® dashboard](https://github.com/apache/apisix-dashboard/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
|
||
- [Apache APISIX® Helm Chart](https://github.com/apache/apisix-helm-chart/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
|
||
- [Docker distribution for Apache APISIX®](https://github.com/apache/apisix-docker/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
|
||
- [Apache APISIX® Website](https://github.com/apache/apisix-website/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
|
||
- [Apache APISIX® Java Plugin Runner](https://github.com/apache/apisix-java-plugin-runner/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
|
||
- [Apache APISIX® Go Plugin Runner](https://github.com/apache/apisix-go-plugin-runner/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
|
||
- [Apache APISIX® Python Plugin Runner](https://github.com/apache/apisix-python-plugin-runner/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
|
||
|
||
## Features
|
||
|
||
You can use Apache APISIX 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.
|
||
|
||
- **All platforms**
|
||
|
||
- Cloud-Native: Platform agnostic, No vendor lock-in, APISIX can run from bare-metal to Kubernetes.
|
||
- Supports ARM64: Don't worry about the lock-in of the infra technology.
|
||
|
||
- **Multi protocols**
|
||
|
||
- [TCP/UDP Proxy](docs/en/latest/stream-proxy.md): Dynamic TCP/UDP proxy.
|
||
- [Dubbo Proxy](docs/en/latest/plugins/dubbo-proxy.md): Dynamic HTTP to Dubbo proxy.
|
||
- [Dynamic MQTT Proxy](docs/en/latest/plugins/mqtt-proxy.md): Supports to load balance MQTT by `client_id`, both support MQTT [3.1.\*](http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html), [5.0](https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html).
|
||
- [gRPC proxy](docs/en/latest/grpc-proxy.md): Proxying gRPC traffic.
|
||
- [gRPC Web Proxy](docs/en/latest/plugins/grpc-web.md): Proxying gRPC Web traffic to gRPC Service.
|
||
- [gRPC transcoding](docs/en/latest/plugins/grpc-transcode.md): Supports protocol transcoding so that clients can access your gRPC API by using HTTP/JSON.
|
||
- Proxy Websocket
|
||
- Proxy Protocol
|
||
- HTTP(S) Forward Proxy
|
||
- [SSL](docs/en/latest/certificate.md): Dynamically load an SSL certificate.
|
||
|
||
- **Full Dynamic**
|
||
|
||
- [Hot Updates And Hot Plugins](docs/en/latest/architecture-design/plugin.md): Continuously updates its configurations and plugins without restarts!
|
||
- [Proxy Rewrite](docs/en/latest/plugins/proxy-rewrite.md): Support rewrite the `host`, `uri`, `schema`, `enable_websocket`, `headers` of the request before send to upstream.
|
||
- [Response Rewrite](docs/en/latest/plugins/response-rewrite.md): Set customized response status code, body and header to the client.
|
||
- Dynamic Load Balancing: Round-robin load balancing with weight.
|
||
- Hash-based Load Balancing: Load balance with consistent hashing sessions.
|
||
- [Health Checks](docs/en/latest/health-check.md): Enable health check on the upstream node and will automatically filter unhealthy nodes during load balancing to ensure system stability.
|
||
- Circuit-Breaker: Intelligent tracking of unhealthy upstream services.
|
||
- [Proxy Mirror](docs/en/latest/plugins/proxy-mirror.md): Provides the ability to mirror client requests.
|
||
- [Traffic Split](docs/en/latest/plugins/traffic-split.md): Allows users to incrementally direct percentages of traffic between various upstreams.
|
||
|
||
- **Fine-grained routing**
|
||
|
||
- [Supports full path matching and prefix matching](docs/en/latest/router-radixtree.md#how-to-use-libradixtree-in-apisix)
|
||
- [Support all Nginx built-in variables as conditions for routing](docs/en/latest/router-radixtree.md#how-to-filter-route-by-nginx-builtin-variable), so you can use `cookie`, `args`, etc. as routing conditions to implement canary release, A/B testing, etc.
|
||
- Support [various operators as judgment conditions for routing](https://github.com/iresty/lua-resty-radixtree#operator-list), for example `{"arg_age", ">", 24}`
|
||
- Support [custom route matching function](https://github.com/iresty/lua-resty-radixtree/blob/master/t/filter-fun.t#L10)
|
||
- IPv6: Use IPv6 to match the route.
|
||
- Support [TTL](docs/en/latest/admin-api.md#route)
|
||
- [Support priority](docs/en/latest/router-radixtree.md#3-match-priority)
|
||
- [Support Batch Http Requests](docs/en/latest/plugins/batch-requests.md)
|
||
- [Support filtering route by GraphQL attributes](docs/en/latest/router-radixtree.md#how-to-filter-route-by-graphql-attributes)
|
||
|
||
- **Security**
|
||
|
||
- Authentications: [key-auth](docs/en/latest/plugins/key-auth.md), [JWT](docs/en/latest/plugins/jwt-auth.md), [basic-auth](docs/en/latest/plugins/basic-auth.md), [wolf-rbac](docs/en/latest/plugins/wolf-rbac.md), [casbin](docs/en/latest/plugins/authz-casbin.md), [keycloak](docs/en/latest/plugins/authz-keycloak.md)
|
||
- [IP Whitelist/Blacklist](docs/en/latest/plugins/ip-restriction.md)
|
||
- [Referer Whitelist/Blacklist](docs/en/latest/plugins/referer-restriction.md)
|
||
- [IdP](docs/en/latest/plugins/openid-connect.md): Support external authentication services, such as Auth0, okta, etc., users can use this to connect to OAuth 2.0 and other authentication methods.
|
||
- [Limit-req](docs/en/latest/plugins/limit-req.md)
|
||
- [Limit-count](docs/en/latest/plugins/limit-count.md)
|
||
- [Limit-concurrency](docs/en/latest/plugins/limit-conn.md)
|
||
- Anti-ReDoS(Regular expression Denial of Service): Built-in policies to Anti ReDoS without configuration.
|
||
- [CORS](docs/en/latest/plugins/cors.md) Enable CORS(Cross-origin resource sharing) for your API.
|
||
- [URI Blocker](docs/en/latest/plugins/uri-blocker.md): Block client request by URI.
|
||
- [Request Validator](docs/en/latest/plugins/request-validation.md)
|
||
- [CSRF](docs/en/latest/plugins/csrf.md) Based on the [`Double Submit Cookie`](https://en.wikipedia.org/wiki/Cross-site_request_forgery#Double_Submit_Cookie) way, protect your API from CSRF attacks.
|
||
|
||
- **OPS friendly**
|
||
|
||
- Zipkin tracing: [Zipkin](docs/en/latest/plugins/zipkin.md)
|
||
- Open source APM: support [Apache SkyWalking](docs/en/latest/plugins/skywalking.md)
|
||
- Works with external service discovery: In addition to the built-in etcd, it also supports [Consul](docs/en/latest/discovery/consul_kv.md) and [Nacos](docs/en/latest/discovery/nacos.md), and [Eureka](docs/en/latest/discovery.md)
|
||
- Monitoring And Metrics: [Prometheus](docs/en/latest/plugins/prometheus.md)
|
||
- Clustering: APISIX nodes are stateless, creates clustering of the configuration center, please refer to [etcd Clustering Guide](https://etcd.io/docs/v3.5/op-guide/clustering/).
|
||
- High availability: Support to configure multiple etcd addresses in the same cluster.
|
||
- [Dashboard](https://github.com/apache/apisix-dashboard)
|
||
- Version Control: Supports rollbacks of operations.
|
||
- CLI: start\stop\reload APISIX through the command line.
|
||
- [Stand-Alone](docs/en/latest/stand-alone.md): Supports to load route rules from local YAML file, it is more friendly such as under the kubernetes(k8s).
|
||
- [Global Rule](docs/en/latest/architecture-design/global-rule.md): Allows to run any plugin for all request, eg: limit rate, IP filter etc.
|
||
- High performance: The single-core QPS reaches 18k with an average delay of fewer than 0.2 milliseconds.
|
||
- [Fault Injection](docs/en/latest/plugins/fault-injection.md)
|
||
- [REST Admin API](docs/en/latest/admin-api.md): Using the REST Admin API to control Apache APISIX, which only allows 127.0.0.1 access by default, you can modify the `allow_admin` field in `conf/config.yaml` to specify a list of IPs that are allowed to call the Admin API. Also, note that the Admin API uses key auth to verify the identity of the caller. **The `admin_key` field in `conf/config.yaml` needs to be modified before deployment to ensure security**.
|
||
- External Loggers: Export access logs to external log management tools. ([HTTP Logger](docs/en/latest/plugins/http-logger.md), [TCP Logger](docs/en/latest/plugins/tcp-logger.md), [Kafka Logger](docs/en/latest/plugins/kafka-logger.md), [UDP Logger](docs/en/latest/plugins/udp-logger.md), [RocketMQ Logger](docs/en/latest/plugins/rocketmq-logger.md), [SkyWalking Logger](docs/en/latest/plugins/skywalking-logger.md), [Alibaba Cloud Logging(SLS)](docs/en/latest/plugins/sls-logger.md), [Google Cloud Logging](docs/en/latest/plugins/google-cloud-logging.md), [Splunk HEC Logging](docs/en/latest/plugins/splunk-hec-logging.md), [File Logger](docs/en/latest/plugins/file-logger.md), [SolarWinds Loggly Logging](docs/en/latest/plugins/loggly.md))
|
||
- [Datadog](docs/en/latest/plugins/datadog.md): push custom metrics to the DogStatsD server, comes bundled with [Datadog agent](https://docs.datadoghq.com/agent/), over the UDP protocol. DogStatsD basically is an implementation of StatsD protocol which collects the custom metrics for Apache APISIX agent, aggregates it into a single data point and sends it to the configured Datadog server.
|
||
- [Helm charts](https://github.com/apache/apisix-helm-chart)
|
||
- [HashiCorp Vault](https://www.vaultproject.io/): Support secret management solution for accessing secrets from Vault secure storage backed in a low trust environment. Currently, RS256 keys (public-private key pairs) or secret keys can be linked from vault in [jwt-auth](docs/en/latest/plugins/jwt-auth.md#enable-jwt-auth-with-vault-compatibility) authentication plugin.
|
||
|
||
- **Highly scalable**
|
||
- [Custom plugins](docs/en/latest/plugin-develop.md): Allows hooking of common phases, such as `rewrite`, `access`, `header filter`, `body filter` and `log`, also allows to hook the `balancer` stage.
|
||
- [Plugin can be written in Java/Go/Python](docs/en/latest/external-plugin.md)
|
||
- [Plugin can be written with Proxy WASM SDK](docs/en/latest/wasm.md)
|
||
- Custom load balancing algorithms: You can use custom load balancing algorithms during the `balancer` phase.
|
||
- Custom routing: Support users to implement routing algorithms themselves.
|
||
|
||
- **Multi-Language support**
|
||
- Apache APISIX is a multi-language gateway for plugin development and provides support via `RPC` and `WASM`.
|
||
|
||
- The RPC way, is the current way. Developers can choose the language according to their needs and after starting an independent process with the RPC, it exchanges data with APISIX through local RPC communication. Till this moment, APISIX has support for [Java](https://github.com/apache/apisix-java-plugin-runner), [Golang](https://github.com/apache/apisix-go-plugin-runner), [Python](https://github.com/apache/apisix-python-plugin-runner) and Node.js.
|
||
- The WASM or WebAssembly, is an experimental way. APISIX can load and run WASM bytecode via APISIX [wasm plugin](https://github.com/apache/apisix/blob/master/docs/en/latest/wasm.md) written with the [Proxy WASM SDK](https://github.com/proxy-wasm/spec#sdks). Developers only need to write the code according to the SDK and then compile it into a WASM bytecode that runs on WASM VM with APISIX.
|
||
|
||
- **Serverless**
|
||
- [Lua functions](docs/en/latest/plugins/serverless.md): Invoke functions in each phase in APISIX.
|
||
- [AWS Lambda](docs/en/latest/plugins/aws-lambda.md): Integration with AWS Lambda function as a dynamic upstream to proxy all requests for a particular URI to the AWS API gateway endpoint. Supports authorization via api key and AWS IAM access secret.
|
||
- [Azure Functions](docs/en/latest/plugins/azure-functions.md): Seamless integration with Azure Serverless Function as a dynamic upstream to proxy all requests for a particular URI to the Microsoft Azure cloud.
|
||
- [Apache OpenWhisk](docs/en/latest/plugins/openwhisk.md): Seamless integration with Apache OpenWhisk as a dynamic upstream to proxy all requests for a particular URI to your own OpenWhisk cluster.
|
||
|
||
## Get Started
|
||
|
||
1. Installation
|
||
|
||
APISIX Installed and tested in the following systems:
|
||
|
||
CentOS 7, Ubuntu 16.04, Ubuntu 18.04, Debian 9, Debian 10, macOS, **ARM64** Ubuntu 18.04
|
||
|
||
Please refer to [install documentation](docs/en/latest/how-to-build.md).
|
||
|
||
2. Getting started
|
||
|
||
The getting started guide is a great way to learn the basics of APISIX. Just follow the steps in [Getting Started](docs/en/latest/getting-started.md).
|
||
|
||
Further, you can follow the documentation to try more [plugins](docs/en/latest/plugins).
|
||
|
||
3. Admin API
|
||
|
||
Apache APISIX provides [REST Admin API](docs/en/latest/admin-api.md) to dynamically control the Apache APISIX cluster.
|
||
|
||
4. Plugin development
|
||
|
||
You can refer to [plugin development guide](docs/en/latest/plugin-develop.md), and sample plugin `example-plugin`'s code implementation.
|
||
Reading [plugin concept](docs/en/latest/architecture-design/plugin.md) would help you learn more about the plugin.
|
||
|
||
For more documents, please refer to [Apache APISIX Documentation site](https://apisix.apache.org/docs/apisix/getting-started/)
|
||
|
||
## Benchmark
|
||
|
||
Using AWS's eight-core server, APISIX's QPS reaches 140,000 with a latency of only 0.2 ms.
|
||
|
||
[Benchmark script](benchmark/run.sh), [test method and process](https://gist.github.com/membphis/137db97a4bf64d3653aa42f3e016bd01) has been open source, welcome to try and contribute.
|
||
|
||
## Apache APISIX vs. Kong
|
||
|
||
#### Both of them have been covered core features of API gateway
|
||
|
||
| **Features** | **Apache APISIX** | **KONG** |
|
||
| :------------------- | :---------------- | :------- |
|
||
| **Dynamic upstream** | Yes | Yes |
|
||
| **Dynamic router** | Yes | Yes |
|
||
| **Health check** | Yes | Yes |
|
||
| **Dynamic SSL** | Yes | Yes |
|
||
| **L4 and L7 proxy** | Yes | Yes |
|
||
| **Opentracing** | Yes | Yes |
|
||
| **Custom plugin** | Yes | Yes |
|
||
| **REST API** | Yes | Yes |
|
||
| **CLI** | Yes | Yes |
|
||
|
||
#### The advantages of Apache APISIX
|
||
|
||
| **Features** | **Apache APISIX** | **Kong** |
|
||
| :-------------------------------------------------------------- | :------------------------------------------------ | :---------------------- |
|
||
| Belongs to | Apache Software Foundation | Kong Inc. |
|
||
| Tech Architecture | Nginx + etcd | Nginx + Postgres |
|
||
| Communication channels | Mail list, Wechat group, QQ group, [GitHub](https://github.com/apache/apisix/issues), [Slack](https://join.slack.com/t/the-asf/shared_invite/zt-nggtva4i-hDCsW1S35MuZ2g_2DgVDGg), meetup | GitHub, Freenode, forum |
|
||
| Single-core CPU, QPS(enable limit-count and Prometheus plugins) | 18000 | 1700 |
|
||
| Latency | 0.2 ms | 2 ms |
|
||
| Dubbo | Yes | No |
|
||
| Configuration rollback | Yes | No |
|
||
| Route with TTL | Yes | No |
|
||
| Plug-in hot loading | Yes | No |
|
||
| Custom LB and route | Yes | No |
|
||
| REST API <--> gRPC transcoding | Yes | No |
|
||
| MQTT | Yes | No |
|
||
| Configuration effective time | Event-driven, < 1ms | polling, 5 seconds |
|
||
| Dashboard | Yes | No |
|
||
| IdP | Yes | No |
|
||
| Configuration Center HA | Yes | No |
|
||
| Speed limit for a specified time window | Yes | No |
|
||
| Support any Nginx variable as routing condition | Yes | No |
|
||
|
||
Benchmark comparison test [details data](https://gist.github.com/membphis/137db97a4bf64d3653aa42f3e016bd01)
|
||
|
||
### Contributor Over Time
|
||
|
||
> [visit here](https://www.apiseven.com/contributor-graph) to generate Contributor Over Time.
|
||
|
||
[](https://www.apiseven.com/en/contributor-graph?repo=apache/apisix)
|
||
|
||
## Videos And Articles
|
||
|
||
- [Apache APISIX: How to implement plugin orchestration in API Gateway](https://www.youtube.com/watch?v=iEegNXOtEhQ)
|
||
- [Improve Apache APISIX observability with Apache Skywalking](https://www.youtube.com/watch?v=DleVJwPs4i4)
|
||
- [APISIX technology selection, testing and continuous integration](https://medium.com/@ming_wen/apache-apisixs-technology-selection-testing-and-continuous-integration-313221b02542)
|
||
- [Analysis of Excellent Performance of Apache APISIX Microservices Gateway](https://medium.com/@ming_wen/analysis-of-excellent-performance-of-apache-apisix-microservices-gateway-fc77db4090b5)
|
||
|
||
## User Stories
|
||
|
||
- [Sina Weibo: the road to customization of Sina Weibo API gateway based on Apache APISIX(Chinese)](https://apisix.apache.org/blog/2021/07/14/the-road-to-customization-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX)
|
||
- [European Factory Platform: API Security Gateway – Using APISIX in the eFactory Platform](https://www.efactory-project.eu/post/api-security-gateway-using-apisix-in-the-efactory-platform)
|
||
- [ke.com: How to Build a Gateway Based on Apache APISIX(Chinese)](https://mp.weixin.qq.com/s/yZl9MWPyF1-gOyCp8plflA)
|
||
- [360: Apache APISIX Practice in OPS Platform(Chinese)](https://mp.weixin.qq.com/s/mF8w8hW4alIMww0MSu9Sjg)
|
||
- [HelloTalk: Exploring Globalization Based on OpenResty and Apache APISIX(Chinese)](https://www.upyun.com/opentalk/447.html)
|
||
- [Tencent Cloud: Why choose Apache APISIX to implement the k8s ingress controller? (Chinese)](https://www.upyun.com/opentalk/448.html)
|
||
- [aispeech: Why we create a new k8s ingress controller? (Chinese)](https://mp.weixin.qq.com/s/bmm2ibk2V7-XYneLo9XAPQ)
|
||
|
||
## Who Uses APISIX?
|
||
|
||
A wide variety of companies and organizations use APISIX for research, production and commercial product, including:
|
||
|
||
<img src="https://user-images.githubusercontent.com/40708551/109484046-f7c4e280-7aa5-11eb-9d71-aab90830773a.png" width="725" height="1700" />
|
||
|
||
Users are encouraged to add themselves to the [Powered By](powered-by.md) page.
|
||
|
||
## Landscape
|
||
|
||
<p align="left">
|
||
<img src="https://landscape.cncf.io/images/left-logo.svg" width="150"> <img src="https://landscape.cncf.io/images/right-logo.svg" width="200" />
|
||
<br /><br />
|
||
APISIX enriches the <a href="https://landscape.cncf.io/card-mode?category=api-gateway&grouping=category">
|
||
CNCF API Gateway Landscape.</a>
|
||
</p>
|
||
|
||
## Logos
|
||
|
||
- [Apache APISIX logo(PNG)](https://github.com/apache/apisix/tree/master/logos/apache-apisix.png)
|
||
- [Apache APISIX logo source](https://apache.org/logos/#apisix)
|
||
|
||
## Acknowledgments
|
||
|
||
Inspired by Kong and Orange.
|
||
|
||
## License
|
||
|
||
[Apache 2.0 License](https://github.com/apache/apisix/tree/master/LICENSE)
|