-
Notifications
You must be signed in to change notification settings - Fork 707
Version Advertisement
Chris Martinez edited this page Jul 29, 2016
·
7 revisions
Splitting implemented service API versions across hosted applications or endpoints is a fairly common scenario. There are several reasons why you might choose to split hosted endpoints, such as different run-time versions or traffic load balancing.
When service API versions are split across deployments, two issues arise:
- The correct service API version cannot be selected across deployments.
- The set of implemented service API versions cannot be aggregated across deployments.
The first issue can be remedied by a using a service gateway. The gateway becomes responsible for obfuscating which endpoints host which API versions. The exact method in which gateways implement this functionality is at the discretion of service authors.
- Home
- Quick Starts
- Version Format
- Version Discovery
- Version Policies
- How to Version Your Service
- API Versioning with OData
- Configuring Your Application
- Error Responses
- API Documentation
- Extensions and Customizations
- Known Limitations
- FAQ
- Examples