Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


A better approach would be to alias /v3/user to /v1/user until there is a breaking change needed in the v3 code tier.


On a rapidly developing API, that would be way too much churn on our front end. For an externally facing API, I completely agree.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: