Fork me on GitHub

Twitter just rolled back their architectural approach for Twitter.com back to a server side implementation.

If you remember back in September of 2010, Twitter rebuilt Twitter.com to use a web application architecture that pushed all of the UI rendering and logic to Javascript running in the browser and consumed the Twitter API directly.

Now they are "taking back control" of their front-end performance by moving the rendering back to the server. They don't say whether they don't use the APIs at all, but I am working under the assumption that they abandoned them.

Twitter felt the API driven web application architecture broke new ground, offered a number of advantages, but it lacked support for various optimization techniques available only on the server.

I was excited to see Twitter go with the API driven approach, along other sites, like the FCC.  I hate to see them abandon it.

What does this say about an API oriented architecture?

Are we not ready? Are there are not enough tools for optimization, or the talent to deliver the performance necessary for Internet at scale via API driven architecture?  Or maybe there are other business reasons for stopping eating their own dog food and going back to a server side architecture?




comments powered by Disqus