API版本控制的最佳实践 [英] Best Practices for API Versioning

问题描述

我正在寻找有关网络服务API版本的建议。



直到现在我们已经使用缓存清单Web应用程序和Web服务来提供离线Web功能。



这意味着我们可以确信用户将获得最新版本的当前API的软件，因此我们只需要管理一个Web服务实例。



我们现在已经进入了各种应用程序商店，我们'不再需要这种类型的控制，并且将不得不管理多个版本的Web服务。



我正在寻找有关任何产品的建议市场可以帮助实现这种类型吗？



我目前的策略是拥有多个应用程序根，每个版本一个。即



http：//mydomain/myapi/v1.0

http：//mydomain/myapi/v1.1

http：//mydomain/myapi/v2.0



还有比这更好的策略吗？

解决方案

本文可以帮助您做出决定： best-practices-version-web- api [ ^ ]

Hi,

I'm looking for advice on web service API versioning.

Until now we've used cache manifest web apps and web services to provide offline web functionality.

This meant that we could be confident that the user would get the latest version of the software for the current API and therefore we only had to manage a single instance of the web service.

We've now moved into the various app stores and we're no longer going to have this type of control and are going to have to manage multiple versions of the web service.

I'm looking for advice on any products in the market place which could aid this type of implementation?

My current strategy is to have multiple application roots, one for each version. I.e.

http://mydomain/myapi/v1.0
http://mydomain/myapi/v1.1
http://mydomain/myapi/v2.0

Are there any better strategies than this?

解决方案

This article may help you to decide: best-practices-version-web-api[^]

这篇关于API版本控制的最佳实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！