Key Concepts Overview
Introduction to the core abstractions and entities in API7 Enterprise.
API7 Enterprise uses a structured set of abstractions to manage API traffic, security, and lifecycle. The pages in this section define each of those concepts and how they relate to each other in a production environment.
Entity relationships
In API7 Gateway, you manage configuration in the control plane, and the control plane delivers it to the data plane instances that belong to each gateway group. A service groups routes, upstreams, and plugins into one API surface.
The following diagram illustrates the relationship between these core entities:
Core abstractions
The table below summarizes the fundamental concepts in API7 Gateway.
| Concept | Description |
|---|---|
| Services and Routes | Grouping of URI-based matching rules (routes) sharing common backend and plugin configurations (services). |
| Upstreams and Load Balancing | Definitions of backend targets, including load balancing algorithms and health checks. |
| Consumers and Credentials | Identity representing an API caller and their associated authentication tokens. |
| Plugins | Modular components that intercept and modify the request/response flow for security, traffic control, and observability. |
| SSL Certificates | TLS assets used to terminate HTTPS traffic and secure client or upstream connections. |
| Gateway Groups | Logical deployment targets that isolate configuration across environments, regions, or teams. |
| Service Discovery | Dynamic upstream endpoint discovery through systems such as Kubernetes, Consul, and Nacos. |
| Stream Routes | Routing rules for TCP and UDP traffic handled by the gateway's stream proxy. |
Next steps
Read each concept page to design and manage your API infrastructure: