Skip to main content


Showing posts from 2014

Architectural principles of RESTful web services

1.  Addressability Addressability is the idea that every object and resource in your system is reachable through a unique identifier. In the REST world, addressability is managed through the use of URIs. Using a unique URI to identify each of your services makes each of your resources linkable. Service references can be embedded in documents. 2. The Uniform, Constrained Interface The idea behind it is that you stick to the finite set of operations of the application protocol you’re distributing your services upon. This means that you don’t have an “action” parameter in your URI and use only the methods of HTTP for your web services. HTTP has a small, fixed set of operational methods. Each method has a specific purpose and meaning (i.e. GET, PUT, DELETE, POST, HEAD, OPTIONS). 3. Representation-Oriented Each service is addressable through a specific URI and representations are exchanged between the client and service. With a GET operation, you are receiving a representation of th