Closed leplatrem closed 6 years ago
Some say versioned API's are evil. Some don't. I'm not aware of any standard set of practices that we enforce to make this the case.
If the application is expected to serve clients across multiple revisions of the application/client, then a versioned API is the safest/easiest method to do so. It would be nice if your app maintained some sort of compatibility between versions/deployments if only to make those deployments easier, but there's no requirement to do so.
Thanks for your reply!
I was looking for an opinionated choice, but it seems like there isn't :)
recommendations on how an API versions it's endpoints are outside the scope of Dockerflow.
Should the application have a version prefix
/v1
? Or should the application serve on/
and the prefix be set during the deployment?