Comments on: on APIs: more craft, less magic

By: Dev Blog AF83 » Blog Archive » Veille technologique : Infrastructure Ruby Rails, HTML, Javascript, Tutoriels, Git, Regexp

Mon, 11 May 2009 22:16:46 +0000

[...] http://www.ultrasaurus.com/sarahblog/2009/05/on-apis-more-craft-less-magic/ : un billet de blog sur les API et leurs utilisations dans Rails [...]

By: clibou

clibou — Mon, 11 May 2009 05:21:58 +0000

checkout Twitter API dev Alex @ Stanford
RT @Al3x Slides from talk today: http://bit.ly/68cej. And video (WMV): http://bit.ly/QrLfS. Of interest if you’re into API design.

By: ste

ste — Thu, 07 May 2009 11:05:24 +0000

“Rails seems to assume that you want to expose your database object model transparently through your API. ”
Rails doesn’t assume this, like it doesn’t assume that you should have an isomorphic mapping between models and controllers. It’s all about exposing resources: the fact that most developers seem to equate resources with models (and, therefore, tend to expose their object model through their APIs) has nothing to do with Rails (well, maybe the guilt is partly to lay on scaffolding, which may have encouraged this mindset)

By: Double Shot #447 « A Fresh Cup

Double Shot #447 « A Fresh Cup — Thu, 07 May 2009 10:23:43 +0000

[...] on APIs: more craft, less magic – “Rails seems to assume that you want to expose your database object model transparently through your API. In my experience, this is rarely what you want to do. In fact, it is a crazy way to live.” [...]

By: Matthew Lang

Matthew Lang — Wed, 06 May 2009 19:56:38 +0000

Great piece Sarah!

It seems that API design has been left out for some time now while Rails developers got fixed on the new application specific features that the framework had to offer.

With the new Rails 3 framework started, and tech like Rails Metal, Rack and Sinatra, more and more developers might start caring more for their API design as well as their application design.