Web Services Foundations 2013
DOI: 10.1007/978-1-4614-7518-7_2
|View full text |Cite
|
Sign up to set email alerts
|

RESTful Web Services: Principles, Patterns, Emerging Technologies

Abstract: RESTful Web services are software services which are published on the Web, taking full advantage and making correct use of the HTTP protocol. This chapter gives an introduction to the REST architectural style and how it can be used to design Web service APIs. We summarize the main design constraints of the REST architectural style and discuss how they impact the design of so-called RESTful Web service APIs. We give examples on how the Web can be seen as a novel kind of software connector, which enables the coo… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
53
0
5

Year Published

2016
2016
2022
2022

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 83 publications
(58 citation statements)
references
References 20 publications
0
53
0
5
Order By: Relevance
“…The principles governing the design of REST APIs are in big part the result of architectural choices of the Web aimed at fostering scalability and robustness of networked, resourceoriented systems based on HTTP [7]. The core principles are [6,23]: Together, these principles explain the name "representational state transfer": interaction state is not stored on the server side; it is carried (transferred) by each request from the client to the server and encoded inside the representation of the resource the request refers to.…”
Section: Rest Apismentioning
confidence: 99%
See 2 more Smart Citations
“…The principles governing the design of REST APIs are in big part the result of architectural choices of the Web aimed at fostering scalability and robustness of networked, resourceoriented systems based on HTTP [7]. The core principles are [6,23]: Together, these principles explain the name "representational state transfer": interaction state is not stored on the server side; it is carried (transferred) by each request from the client to the server and encoded inside the representation of the resource the request refers to.…”
Section: Rest Apismentioning
confidence: 99%
“…Along with the general principles introduced above, a set of implementation best practices have emerged to guide the design of quality APIs [23,16,19,22]. These best practices address the main design aspects in REST APIs: (i) the modeling of resources, (ii) the identification of resources and the design of resource identifiers (URIs), (iii) the representation of resources, (iv) the definition of (HTTP) operations on resources, and (v) the interlinking of resources.…”
Section: Best Practices For Developmentmentioning
confidence: 99%
See 1 more Smart Citation
“…An evaluation of RESTful Web services that are consumed from mobile devices is presented in [18] but this evaluation is limited to mobile Web service consumers and does not include mobile Web service providers. The concept of REST-based Mobile Web services is introduced in [22]and a comparison with SOAP is carried out in [19], [20]and [4]. On the other hand, implementation of mobile hosts based on REST is not addressed.…”
Section: State Of the Artmentioning
confidence: 99%
“…In general, our approach generates executable clients for remote APIs that are formally deined in terms of OpenAPI [10] speciications, which has been proposed as a machine-readable format for describing the architecture of services ofered as RESTful remote APIs [11]. Moreover, resilience is achieved by specifying service policies, such as rate limits and pagination, and handling them, as well as network failures and response caching, accordingly and in a graceful and transparent manner.…”
Section: Introductionmentioning
confidence: 99%