Route entities define rules to match client requests.
Each Route is associated with a Service,
and a Service may have multiple Routes associated to it.
Every request matching a given Route will be proxied to its associated Service.
The combination of Routes and Services (and the separation of concerns between them)
offers a powerful routing mechanism with which it is possible to
define fine-grained entry-points in Kong
leading to different upstream services of your infrastructure.
The Consumer object represents a consumer - or a user - of a Service.
You can either rely on Kong as the primary datastore,
or you can map the consumer list with your database to keep consistency between Kong and your existing primary datastore.