When we originally released the Twitter API back in 2006, little thought was given to API design patterns like explicit versioning, subdomain partitioning, and response structures that would scale with the rapid but unexpected growth of the Twitter service and platform. Over the past two years we’ve continued refining and upgrading our original API and the monolithic infrastructure that powered it.Read more…