One thing’s for sure. If you don’t have to version your API, do not try to do that. However, sometimes you have to. Many of the most popular services like Twitter, Facebook, Netflix, or PayPal are versioning their REST APIs. The advantages and disadvantages of that approach are obvious. On the one hand, you don’t have to worry about making changes in your API even if many external clients and applications consume it. But on the other hand, you have to maintain different versions of API implementation in your code, which sometimes may be troublesome.
In this article, I’m going to show you how to maintain the several versions of REST APIs in your application in the most comfortable way. We will base this article on a sample application written on top of the Spring Boot framework and exposing API documentation using Swagger2 and SpringFox libraries. https://goo.gl/uoEG4d #DataIntegration #ML
