How apache/apisix works
Apache APISIX is a dynamic API/AI gateway. The documented request path is: an administrator configures a route, a client request enters the gateway, traffic is matched and managed, and the request is proxied to an upstream service. The supplied tree is a partial snapshot dominated by tests and examples; it does not include the gateway runtime or most feature implementations. Accordingly, the graph captures documented product stages and capabilities, but cannot assign source paths to those unsupplied components. Edges are based on the README rather than inspected runtime code.
Components 15
Configuration
- Admin API
- Route configuration
Gateway traffic
- APISIX gateway
- Dynamic routing
Traffic capabilities
- Load balancing
- Retries and resilience
- Traffic control
- Authentication and security
- Observability
Protocols and integrations
- AI proxying
- Protocol proxies
Other components
- Administrator
- API client
- Upstream service
- etcd configuration store
Connections 13
- Administrator → Admin API: configures
- Admin API → Route configuration: sets routes
- API client → APISIX gateway: sends request
- APISIX gateway → Dynamic routing: matches route
- Dynamic routing → Upstream service: proxies request
- APISIX gateway → Load balancing: balances traffic
- APISIX gateway → Retries and resilience: manages failures
- APISIX gateway → Traffic control: controls traffic
- APISIX gateway → Authentication and security: secures traffic
- APISIX gateway → Observability: provides observability
- APISIX gateway → AI proxying: routes AI traffic
- APISIX gateway → Protocol proxies: proxies protocols
- APISIX gateway → etcd configuration store: uses configuration store