Identifying Resources The key parts of a Resource oriented architecture are resources, identifiers, representations and the links between them.Designing a RESTful system starts with identifying resources. Resource identification is generally the most flexible aspect of designing a REST based system. There is no exact science to identifying resources and there is no right or wrong … Continue reading Identifying Resources and URI design.
The Richardson Maturity Model was developed by Leonard Richardson. It specifies a model to grade REST services according to their adherence to the REST constraints.This model identifies three levels of service maturity based on the service's support for URI's, HTTP and Hypermedia.The level 0 represents a basic Level Zero Services - Level zero services are characterized … Continue reading Richardson’s Maturity Model
The REST architectural constraints specify a model to build services which are better optimized to use the standard infrastructural elements
Implementing HTTP’s uniform interface as discussed in the previous posts has a surprisingly good architectural side effect. If it is Implemented as specified in the REST specifications (HTTP specification - RFC 2616), you get two useful properties namely Idempotency and Safety . Safety is the ability to invoke an operation without any side effects arising out of … Continue reading Rest – Idempotency and Safety
Overview of HTTP In my previous post we talked about REST resources, Identifiers and Representations. In this post we move forward with how we can connect the various resources and their representations through their identifiers using the HTTP protocol. In a RESTful system, clients and servers interact only by sending each other messages that follow a … Continue reading Rest – Communicating with Verbs and status codes