Skip to main content

Apache APISIX

Apache APISIX is an open-source cloud-native Application Programming Interface (API) gateway and microservices traffic management platform (API management) built on top of NGINX and etcd and hosted by The Apache Software Foundation.

  • Cloud-native API gateway and microservices ingress (API management, traffic management)
  • Dynamic routing, load balancing, and traffic splitting for north-south and east-west traffic (traffic management)
  • Plugin-based extensibility for authentication, security, observability, and transformations (extensibility, security, observability)
  • Integration with service discovery, configuration, and control planes using etcd and other backends (service discovery, configuration management)
  • Supports deployment across bare metal, virtual machines, containers, and Kubernetes (infrastructure, container orchestration)

More About Apache Apisix

Apache APISIX is an open-source, cloud-native API gateway and microservices traffic management platform (API management, traffic management) under The Apache Software Foundation. The project focuses on managing and governing API and microservice traffic, handling north-south traffic from clients into back-end services and east-west traffic between services. It is designed around a dynamically configurable control plane and a data plane built on NGINX and etcd, with configuration changes taking effect without reloads.

APISIX provides routing and traffic control functions (traffic management) such as URI- and host-based routing, header and query parameter matching, and load balancing across upstream services. It supports canary releases and traffic splitting (release management, traffic shaping), enabling gradual rollouts and A/B scenarios by directing specific traffic percentages or rules to selected upstreams. These capabilities are configured via declarative configuration or APIs and can be integrated into Continuous Integration and Continuous Deployment (CI/CD) workflows.

The project exposes a plugin system (extensibility) that allows users to enable and compose features at the route, service, or consumer level. Available plugin categories include authentication and authorization (security, identity and access), such as key-based auth, JWT-based auth, and other credential-based approaches; security controls (security) like IP restriction and rate limiting; and data plane extensions such as request and response transformation, header rewriting, and body modification (API mediation). APISIX also provides observability plugins (observability, monitoring) that integrate with logging and metrics backends for access logs, tracing, and real-time monitoring of traffic.

In enterprise environments, APISIX is used as an ingress gateway and centralized API entry point (API management, ingress). It can run on bare metal, virtual machines, containers, and Kubernetes clusters, integrating with container orchestration platforms as an ingress controller. Its dynamic configuration model (configuration management) allows operators to adjust routes, plugins, and upstream definitions without restarting the data plane, which aligns with automated infrastructure and GitOps practices. The system can integrate with service discovery backends (service discovery) so that upstream instance lists update automatically.

APISIX supports Transport Layer Security (TLS) termination and mutual TLS (network security) for secure transport, enabling encrypted client connections and secure upstream communication. It also offers features such as health checks and circuit-breaking-style controls (resilience, reliability engineering) to maintain availability when back-end services are unhealthy. Built-in dashboard and control-plane tooling (operations tooling) are available for administration and visualization, and APISIX can also be driven purely through APIs or configuration files.

From a directory and taxonomy perspective, Apache APISIX is categorized as an API gateway and microservices ingress layer (API management, microservices networking). It also fits into traffic management, service mesh edge gateway, and observability integration categories, due to its routing, security, and metrics/logs integration capabilities. Its plugin architecture and protocol support place it within extensible, cloud-native network middleware that connects clients, services, and infrastructure components across heterogeneous deployment environments.