Geek asks and answers

Is api.example.com better than example.com/api?

It seems that most of the popular RESTful APIs prefer subdomains over subdirectories:

  • api.twitter.com
  • api.linkedin.com
  • api.foursquare.com
  • graph.facebook.com

I was wondering if there were any technical arguments.

+3
source share
3 answers

This is load balancing.

We have twitter.com address 199.59.150.39
We have twitter.com address 199.59.149.230
We have twitter.com address 199.59.150.7
We have api.twitter.com address 199.59.150.9
We have api.twitter.com address 199.59.149.232
In api.twitter.com has the address 199.59.148.20
api.twitter.com has the address 199.59.148.87

api.linkedin.com 216.52.242.83
linkedin.com 216.52.242.86

api.foursquare.com 50.19.210.39
foursquare.com 50.16.220.173

graph.facebook.com 66.220.146.87
facebook.com 66.220.158.11
facebook.com 69.171.229.11
facebook.com 69.171.242.11
facebook.com 66.220.149.11

, - API -. , Twitter Ruby, Scala. - , API, , .

, API , ( Twitter, API).

+3

-, , AJAX. domain.com, AJAX sub.domain.com.

0

If you want the API service to use a different server (large scale) api.domain.com, it is better, but you want AJAX on a medium or small scale to domain.com/apibe better.

0
source

More articles:


All Articles