Web Services Are Not Distributed Objects
IEEE Internet Computing
Communications of the ACM - Web science
Restful web services vs. "big"' web services: making the right architectural decision
Proceedings of the 17th international conference on World Wide Web
Communications of the ACM
RPC and REST: Dilemma, Disruption, and Displacement
IEEE Internet Computing
VoCS'08 Proceedings of the 2008 international conference on Visions of Computer Science: BCS International Academic Conference
A finite-state machine approach for modeling and analyzing restful systems
Journal of Web Engineering
A concept for generating simplified RESTful interfaces
Proceedings of the 22nd international conference on World Wide Web companion
| Hi-index | 0.00 |
Recent technology trends in Web services indicate that a solution eliminating the perceived complexity of the WS-* standard technology stack may be in sight: advocates of Representational State Transfer (REST) have come to believe that their ideas explaining why the World Wide Web works are just as applicable to solve enterprise application integration problems and to radically simplify the plumbing required to implement a Service-Oriented Architecture (SOA). In this tutorial we give an introduction to the REST architectural style as the foundation for RESTful Web services. The tutorial starts from the basic design principles of REST and how they are applied to service oriented computing. Service-orientation concentrates on identifying self-contained units of functionality, which should then be exposed as easily reusable and repurposable services. This tutorial focuses not on the identification of those units, but on how to design the services representing them. We explain how decisions on the SOA level already shape the architectural style that will be used for the eventual IT architecture, and how the SOA process itself has to be controlled to yield services which can then be implemented RESTfully. We do not claim that REST is the only architectural style that can be used for SOA design, but we do argue that it does have distinct advantages for loosely coupled services and massive scale, and that any SOA approach already has to be specifically RESTful on the business level to yield meaningful input for IT architecture design.