Hi,
Is there some best industry practices or guidelines for the anatomy of a resource URL for an upstream service being exposed via Kong?
A general URL anatomy while fetching a resource as per rest guidelines is something like -
https://sub-domain.top-level-domain/path/api/api-building-block/version/resource-name/resource-id
While exposing an URL through Kong is it the same guidelines that should be followed? I mean for example, when Kong is deployed in a multi-tenant environment, I might need to also like to have my tenant name included as part of the URL to avoid conflict resolution.
Also, how about the versioning? Is it something required to be exposed out or something that needs to be handled between Kong Service & upstream service and not getting this reflected to end user.
Could anyone help me here?
Br,
Sanjit