Monday, August 23, 2004

The best of REST

Implementing REST Web Services: Best Practices and Guidelines " The architecture represented above has a pipe-and-filter style, a classical and robust architectural style used as early as in 1944 by the famous physicist, Richard Feynman, to build the first atomic bomb in his computing team. A request is processed by a chain of filters and each filter is responsible for a well-defined unit of work. Those filters are further classified as two distinct groups: front-end and back-end. Front-end filters are responsible to handle common Web service tasks and they must be light weight. Before or at the end of front-end filters, a response is returned to the invoking client...Most notably, the filters can be considered as a standard form of computing and new filters can be added or extended from existing ones easily. This architecture has good user-perceived performance because responses are returned as soon as possible once a request becomes fully processed by lightweight filters. This architecture also has good security and stability because security breakage and errors can only propagate a limited number of filters."

Web Services: REST in Peace? "The advantages of conceptualising an application in terms of services and messages, rather than in terms of APIs (either RESTful or RPC oriented varieties) are clear: it enables super-loose coupling both for composing services into applications and in the implementation of a service itself."

2 comments:

Andrew said...

Semantic Clarity is where I linked to "Triple-based Computing" which also mentions Semantic Web bringing clarity to the Universal Server concept.

Mark Baker said...

Henry - Actually, POST just means "process this data". Resource creation is one possible result of data processing, but not a necessary one.