16 May '13, 1am

Version your API without versioning your controllers or your URLs. @robb1e

There are many blogs about how to expose an API for a Rails application and many times I look at this and am concerned about how these examples often leak the application design and the schema out through the API. When this leak occurs a change to the application internals can ripple out and break clients of an API, or force applications to namespace URI paths which I feel is unnecessary and ugly. When the only consumer of application data models are the views within the same application then the object design can be fluid and malleable. Once an application exposes an API to more than one client, and especially if that client is on a different release cycle to the server, such as iPhone application, data models become rigid. Rails tends discouraged N-tier architecture to the benefit of development speed but APIs are contracts between a server and it’s client and can be dif...

Full article: http://pivotallabs.com/stop-leaky-apis/

Tweets

Creating consistent APIs with

rubyflow.com 13 May '13, 4am

Creating consistent APIs with jsonapi.org Posted by nesquena on May 13, 2013 — 0 comments Yehuda Katz and Steve Klabnik re...

Useful! Jonathan Berger offers "7 Best Practice...

pivotallabs.com 15 May '13, 3pm

Facilitating a retro is a very powerful role; it’s almost akin to being a courthouse judge (and stenographer). By asking q...

ASCIIcast 414 - Batch API Requests (pro)

railscasts.com 12 May '13, 9pm

Apr 27, 2013 | 18 minutes | Rack , APIs Here I demonstrate how to perform bulk API operations though a single request usin...