API location

If anyone still follows this blog, I’d like to know your thoughts on where to put the API in TightURL.

  1. http://example.com/api
  2. http://api.example.com

My guess is the main argument for choice 2 is that it makes scaling easier, which shouldn’t be a concern for TightURL users, none of whom are to my knowledge running a major URL shortening service.*

The main argument in favor of choice 1, as far as I’m concerned, is that it keeps with an original design principle in TightURL, that all URLs on a TightURL site branch off the web root.  As it turns out, this seems to be a design principle in REST as well.

Thoughts?

[*] TightURL has for some time, been developed under the belief that the demonstration/reference implementation copy running at tighturl.com is the one with the most traffic, and that at any given time, if TightURL is able to handle the load at tighturl.com, then it should handle the load for all the other users as well.

This entry was posted in Uncategorized and tagged , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *