Posted on 05-29-2012
Twitter just rolled back their architectural approach for Twitter.com back to a server side implementation.
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
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Viewbook Uses Flickr API Design When Designing Their Own
- Expanding An API Designers Horizon Using Apiary
- What Version Of The API Economy Are You Investing In?
- I Am Up To 34 APIs Out Of The Netherlands
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?
- A Better Understanding Of Government APIs And Their Consumers Before Considering Charging For Use
- So You Wanna Do a Spreadsheet or Database To API Startup
- Jumpstarting the Automobile API Conversation With Carvoyant