News for hackers. Stuff that matters.

A comment on The largest Git repo. Parent comment

Re:The largest Git repo by jjawssd on Wednesday May 24, 2017 @09:51PM (#14414801)
Use namespaces to separate API versions?

POST /v4/whatever

POST /v3/whatever

[ Parent | on HN ]
Re:The largest Git repo by _asummers on Friday May 26, 2017 @04:21PM (#14426847)
We version each of our individual resources. so a /v1/user might have many /v3/post . Seems to work for us as a smaller engineering team.
[ Parent | on HN ]
Re:The largest Git repo by jjawssd on Tuesday May 30, 2017 @12:10PM (#14446303)
A better approach would be to alias /v3/user to /v1/user until there is a breaking change needed in the v3 code tier.
[ Parent | on HN ]
Re:The largest Git repo by _asummers on Thursday June 01, 2017 @08:17AM (#14459621)
On a rapidly developing API, that would be way too much churn on our front end. For an externally facing API, I completely agree.
[ Parent | on HN ]