Restful web services vs. "big"' web services: making the right architectural decision

By Cesare Pautasso, Olaf Zimmermann, Frank Leymann. The Web Conference, 2008

1,087 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems, Management Information Systems

View Paper: https://www.semanticscholar.org/paper/e0ed8f47642c8e1aae2455dd4d842f0fc497d16b

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Networks and Communications

In Information Systems

In Management Information Systems

Citations in the corpus

Towards the Web of Things: Web Mashups for Embedded Devices (2009, background): “The simplicity of REST and its seamless intergration into global networks makes it an ideal candidate for creating “tactical, ad-hoc integration over the Web” [18].”
The Web of Things: A Survey (Invited Paper) (2011, background): “For example, according to [26], REST is the architecture of choice for tactical, ad hoc integration over the Web (i.e., mashup).”
Interoperability in Internet of Things: Taxonomies and Open Challenges (2018, neutral): “A study conducted by Pautasso et al [70] compared REST web services with WS-* servers and they concluded that RESTful services are preferred for tactical, ad-hoc integration over the Web, while WS-* are preferred for professional enterprise application integration scenarios.”
The Internet of Things (2018, positive): “Simplicity of REST application programming interfaces (APIs) has resulted in rapid development of highly consumable services, through power of reuse [14, 15].”
Computation Offloading Toward Edge Computing (2019, methodology): “It provides a RESTful [204] development model to encapsulate computation capabilities based on serverless cloud containers (similar to Amazon AWS Lambda [144]).”
Interacting with the SOA-Based Internet of Things: Discovery, Query, Selection, and On-Demand Provisioning of Web Services (2010, background): “For lightweight and more end-user oriented applications, the RESTful approach offers significant advantages such as simplicity, direct web integration, and looser-coupling [4], [26].”
The SAMS: Smartphone Addiction Management System and Verification (2013, methodology): “Second, the view and transport part is implemented following RESTful [12] methods, i.e., using HTTP and JSON.”