News for hackers. Stuff that matters.

A comment on Considerations When Planning Endpoints for your RESTful API.

Re:Considerations When Planning Endpoints for your RESTful API by dieselz on Wednesday October 19, 2011 @01:50AM (#3128917)
Your reasoning for having the api at a subdomain applies for versioning is well. Imagine v1 of the api is written quickly in PHP. As the needs of the company change, you may need to iterate on the api and build v2 with Java. Managing versions by api.example.com/v1 and api.example.com/v2 would be difficult. Here are two suggestions: v1.api.example.com or v1api.example.com.
[ Parent | on HN ]
Re:Considerations When Planning Endpoints for your RESTful API by johns on Wednesday October 19, 2011 @03:50AM (#3129171)
Routing on the path is trivial for many different proxies.
[ Parent | on HN ]
Re:Considerations When Planning Endpoints for your RESTful API by bromley on Wednesday October 19, 2011 @04:06AM (#3129200)
Yes but you still need a proxy. With versioning in the subdomain you can easily route requests for different versions to completely different systems. That flexibility might come in handy one day.
[ Parent | on HN ]
Re:Considerations When Planning Endpoints for your RESTful API by vog on Wednesday October 19, 2011 @05:50AM (#3129424)
In how far is this less effort than the proxy? In the one case you add a line to your web server config, in the other case to your DNS server config.
[ Parent | on HN ]