@article {2018:ieeesw,
	title = {The Web as a Software Connector: Integration Resting on Linked Resources},
	journal = {IEEE Software},
	volume = {35},
	year = {2018},
	month = {January/February},
	pages = {93 - 98},
	abstract = {The web, seen as a graph of linked resources shared between microservices, can serve as an integration style. It offers unique characteristics and possibilities regarding dataflow, control flow, and other qualities, compared to file transfer, shared databases, remote procedure calls, and asynchronous messaging. Carrying these insights in your toolbox will make you aware of all the options to consider next time you build loosely coupled integrated systems.},
	keywords = {coupling, REST, software architecture},
	doi = {10.1109/MS.2017.4541049},
	url = {http://ieeexplore.ieee.org/document/8239944/},
	author = {Cesare Pautasso and Olaf Zimmermann}
}
@conference {www08restsoap,
	title = {RESTful Web Services vs. Big Web Services: Making the Right Architectural Decision},
	booktitle = {17th World Wide Web Conference (WWW 2008)},
	year = {2008},
	month = {April},
	pages = {805-814},
	publisher = {ACM},
	organization = {ACM},
	address = {Beijing, China},
	abstract = {Recent technology trends in the Web Services (WS) domain indicate that a solution eliminating the presumed complexity of the WS-* standards 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 simplify the plumbing required to build service-oriented architectures. In this paper we objectify the WS-* vs. REST debate by giving a quantitative technical comparison based on architectural principles and decisions. We show that the two approaches differ in the number of architectural decisions that must be made and in the number of available alternatives. This discrepancy between freedom-from-choice and freedom-of-choice explains the complexity difference perceived. However, we also show that there are significant differences in the consequences of certain decisions in terms of resulting development and maintenance costs. Our comparison helps technical decision makers to assess the two integration styles and technologies more objectively and select the one that best fits their needs: REST is well suited for basic, ad hoc integration scenarios, WS-* is more flexible and addresses advanced quality of service requirements commonly occurring in enterprise computing. },
	keywords = {architectural decisions, REST, SOAP, Web services},
	doi = {10.1145/1367497.1367606},
	author = {Cesare Pautasso and Olaf Zimmermann and Frank Leymann}
}
