> If you want to expose extra features or change the api design, you version your api. But you are still coupled. If you have to version your API that means i

> If you want to expose extra features or change the api design, you version your api. But you are still coupled. If you have to version your API that means it is relied on by something else and in order to use that extra feature still requires both (or more) services to all be on the same page. Microservices let you deploy and maintain at different times (if that is appealing to you) but in order to realize a new business feature you are still coupled. Now you have x tests for x versions as well, make sure the old version remains old and the new feature works in the new version.