Routes

Routes in a service define paths to upstream nodes. A route matches client requests based on configured rules, load and execute related plugins, and forward requests to the specified upstream nodes. A route must belong to a single service. It cannot be isolated or shared across multiple services.

You can set a simple route with a path-matching URI and methods. The diagram illustrates how to send two HTTP requests to the API7 Enterprise, which are then forwards based on the configured rules in routes:

Version Control

API7 Enterprise exclusively offers version control at the service level. Any modifications made to any route within a service are treated as a new service version when publishing it to gateway groups.

Related Topic

• If you have interest in applying plugins on a route, see this doc (coming soon).