Representational State Transfer. A model for resource interaction that scales like the World Wide Web - is Generative - so even if designing an Enterprise architecture you get more scalability and flexibility.

Richardson Maturity Model - Leonard Richardson

  • Mar'2010: Martin Fowler comments

  • May'2011: Duncan Cragg comments. Among other things: *So don't get stressed out about just using HttpPost - as long as you're being Declarative and not tunnelling Imperative function calls:

    • Use POST the way the Web does: to return whole data structures in an agreed, stable domain-specific format over a common base Media Type
    • Use POST the way the Web should have done: idempotently! Which means putting enough identifying information in the content so that you can tell if you've seen it already
    • POST to real, HttpGet-able resources .. and don't forget to invalidate the cache of that resource as the POST flies by*

Restful Web Services by Leonard Richardson and Sam Ruby

excellent explanation of the value/simplicity of ReST and HTTP.

the FAQ includes some interesting notes on application of ReST approach to things you wouldn't normally associate HTTP with - e.g. Instant Messaging, and compares it to SOAP.


one key concept is that each schema stays focused on just describing some data - then when add different functions/requirements, you just pass that data to a new URI associated with that transaction. That smells like a nice thing...

Documenting ReST API

Python Web Framework- and ReST


and AJAX

Joe Gregorio, example URI-s


Zope support < Zope.html>

ROCA: Resource Oriented Client Architecture

Edited:    |       |    Search Twitter for discussion