API Proxy Versioning vs API Versioning

Shouldn't we keep API Proxy versioning separate from the actual backend-api endpoint?

say for example, In an enterprise application , there are 50 APIs and around 25 proxies created for those 50 APIs. and the backend-api versioning is following some pattern like /api/v1/resourcename

What is the best practice for the Proxy versioning ?

0 2 696
2 REPLIES 2

Versioning has to change whenever your contracts change and if backend services follow a good versioning strategy that your proxies reflect, then stick to it, also Just update versioning on the upgraded backend services, leave the others as they are if no contract changes are present IMHO.

can we keep both the backend api anf the api proxy maintain the same version?