In this post I continue with the review of one of the classical references about this topic, the book “RESTful Web Services” by L. Richardson & S. Ruby (O’Reilly 2007). Even though it could be considered an old reference and even the authors recognize that the ROA term could be controversial, for lots developers this books is the first step in the path of web programming. Additional post will follow this one.
In term of ROA concepts, design web services means turning requirements into resources specifications. From those specifications, a "real" web services can be implemented in whatever programming language and deployed in a web server.
The "Restful web service" reference proposes the following methodology:
- Figure out the web service data set.
- Split the data set into resources, defining:
- the name of the resources with URI.
- the subset of method of the uniform interface for those resources.
- representations accepted from and server to the client.
- hypermedia links between resources.
- Interactions and error (dynamic) between client and server.