Resource-Oriented Architecture (ROA) and REST
TS-5173

Google quietly deprecated its SOAP search API at the end of 2006. Although this doesn't mean that you should abandon SOAP, it does reflect a growing trend toward simpler dialects of Web services. Google joins several popular Web sites (Yahoo!, Amazon, eBay, and others) that offer all the benefits of Web services without all of the complexity of SOAP.

This session looks at the semantic differences between a service-oriented architecture and a resource-oriented architecture. It contrasts RPC-centric interfaces with object-oriented interfaces. It discusses HTTP-RPC services that call themselves RESTful and compares them with fully RESTful Web services that leverage HTTP verbs such as GET, POST, PUT, and DELETE. And it looks at RESTful implementations using Java Servlet APIs and exploiting Grails' native REST support.