scholarly journals Evaluating a Representational State Transfer (REST) Architecture

2020 ◽  
Author(s):  
Bruno Costa ◽  
Paulo Pires
Keyword(s):  
Quality Attribute ◽  
Architectural Style ◽  
Representational State Transfer ◽  
Design Considerations ◽  
Trade Offs ◽  
State Transfer ◽  
Architecture Evaluation ◽  
New Challenges ◽  
Representational State ◽  
And Performance

The use of Representational State Transfer (REST) as an architectural style for integrating services and applications brings several benefits, but also poses new challenges and risks. Particularly important among those risks are failures to effectively address quality attribute requirements such as security, reliability, and performance. An architecture evaluation can identify and help mitigate those risks. In this work we present guidelines to assist architecture evaluation activities in REST-based systems. These guidelines can be systematically used in conjunction with scenario-based evaluation methods to reason about design considerations and trade-offs. This work also present the results of a survey conducted with industry specialists who have performed architecture evaluations in real world REST-based systems in order to gauge the suitability and utility of the proposed guidelines.

scholarly journals Http Relay Binding (webHttpRelayBinding) and Crud Contract

2019 ◽  
pp. 51-54
Author(s):  
Dr. Manish L Jivtode
Keyword(s):  
World Wide Web ◽  
Web Services ◽  
Web Service ◽  
World Wide ◽  
Distributed Applications ◽  
Configuration File ◽  
Representational State Transfer ◽  
State Transfer ◽  
Representational State ◽  
Http Protocol

The Broker Architecture became popular involving client and server. Representational State Transfer(REST) architecture is the architecture of World Wide Web. REST uses HTTP protocol based on Servlet and ASMX technology is replaced by WCF web service technology. SOAP and REST are two kinds of WCF web services. REST is lightweight compared to SOAP and hence emerged as the popular technology for building distributed applications in the cloud. In this paper, conducted by exposing a HTTP endpoint address, HTTP relay binding (webHttpRelayBinding) and CRUD contract through interface. The interface is decorated using WebGet and WebInvoke attributes. WCF configuration file created using XML tags for use with REST web service.

scholarly journals BioInstaller: a comprehensive R package to integrate bioinformatics resources

2018 ◽  
Author(s):  
Jianfeng Li ◽  
Bowen Cui ◽  
Yuting Dai ◽  
Ling Bai ◽  
Jinyan Huang
Keyword(s):  
Source Code ◽  
R Package ◽  
Community Based ◽  
Representational State Transfer ◽  
State Transfer ◽  
Application Programming ◽  
Representational State ◽  
Programming Interfaces ◽  
Shiny Application ◽  
R Functions

The number of bioinformatics resources, such as tools/scripts and databases are growing exponentially. This poses a great challenge for users to access, manage, and integrate the corresponding bioinformatics resources. To facilitate the request, we proposed a comprehensive R package, BioInstaller, which includes the R functions, Shiny application, and the HTTP representational state transfer (REST) application programming interfaces (APIs). We also established a community-based configuration pool to collect, access and share bioinformatics resources. The source code of BioInstaller is freely available at our lab website http://bioinfo.rjh.com.cn/labs/jhuang/tools/bioinstaller or popular package host GitHub at: https://github.com/JhuangLab/BioInstaller. Also, a docker image can be downloaded from DockerHub (https://hub.docker.com/r/bioinstaller).

Enterprise Integration With the Structural Services Architectural Style

2019 ◽  
pp. 352-392 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Architectural Style ◽  
Enterprise Integration ◽  
Representational State Transfer ◽  
Advantages And Disadvantages ◽  
Architectural Styles ◽  
State Transfer ◽  
Enterprise Applications ◽  
Service Oriented ◽  
Structural Compliance

The Service-Oriented Architecture (SOA) and Representational State Transfer (REST) architectural styles are the most used for the integration of enterprise applications. Each is more adequate to a different class of applications and exhibits advantages and disadvantages. This chapter performs a comparative study between them. It is shown that SOA and REST are dual architectural styles, one oriented towards behavior and the other towards state. This raises the question of whether it is possible to combine them to maximize the advantages and to minimize the disadvantages. A new architectural style, Structural Services, is proposed to obtain the best characteristics from SOA and REST. As in SOA, services are able to offer a variable set of operations and, as in REST, resources are allowed to have structure. This style uses structural interoperability, based on structural compliance and conformance. A service-oriented programming language is also introduced to instantiate this architectural style.

Improving Application Integration by Combining Services and Resources

2019 ◽  
pp. 197-226 ◽  
Author(s):  
José Carlos Martins Delgado
Keyword(s):  
Service Oriented Architecture ◽  
Application Integration ◽  
Architectural Style ◽  
Representational State Transfer ◽  
Architectural Styles ◽  
State Transfer ◽  
Fixed Set ◽  
Service Oriented ◽  
Application Developers ◽  
Bare Minimum

The main application integration approaches, the service-oriented architecture (SOA) and representational state transfer (REST) architectural styles, are rather different in their modeling paradigm, forcing application developers to choose between one and the other. In addition, both introduce more application coupling than required, since data schemas need to be common, even if not all instantiations of those schemas are used. This chapter contends that it is possible to improve this scenario by conceiving a new architectural style, structural services, which combines services and resources to reduce the semantic gap with the applications, allowing to tune the application integration between pure service-based and pure resource-based, or an intermediate mix. Unlike REST, resources are not constrained to offer a fixed set of operations, and unlike SOA, services are allowed to have structure. In addition, compliance is used to reduce coupling to the bare minimum required by the actually used application features.

Pemantauan dan Pengendalian Parameter Akuaponik Menggunakan Representational State Transfer Application Programming Interface

2020 ◽  
Vol 9 (4) ◽  
pp. 394-402
Author(s):  
Helmy ◽  
Athadhia Febyana ◽  
Agung Al Rasyid ◽  
Arif Nursyahid ◽  
Thomas Agung Setyawan ◽  
...  
Keyword(s):  
Application Programming Interface ◽  
Total Dissolved Solids ◽  
Data Loss ◽  
Representational State Transfer ◽  
State Transfer ◽  
Application Programming ◽  
Representational State ◽  
Rest Api ◽  
E Mail ◽  
Programming Interface

Akuaponik merupakan penggabungan antara akuakultur dengan hidroponik. Salah satu sistem hidroponik yaitu sistem drip (tetes). Parameter yang perlu diperhatikan dalam budidaya akuaponik antara lain keasaman larutan nutrisi yaitu pH, suhu air, dan larutan nutrisi yang ditunjukkan oleh kepekatan zat padat terlarut dalam air (Total Dissolved Solids, TDS). Nutrisi tanaman diperoleh dari kotoran ikan yang mengandung nitrogen. Oleh karena itu, diperlukan pemantauan pH, TDS, dan suhu secara realtime dan pengendalian kelembapan tanah pada tanaman akuaponik agar tanaman tidak kekurangan nutrisi. Proses pengendalian menggunakan Representational State Transfer Application Programming Interface (REST API) dalam menerima nilai batas ambang yang ditentukan petani akuaponik melalui situs web dan mengirimkan nilai kelembapan tanah dan parameter kolam ikan berupa pH, suhu dan TDS ke server. Pengujian data loss dan delay pada sistem pemantauan dan pengendalian ini diperlukan untuk mengetahui keandalan alat dalam pengiriman dan penerimaan data. Selain itu, diperlukan notifikasi berupa e-mail kepada petani apabila nilai kelembapan tanah kurang dari batas ambang. Hasil pengujian menunjukkan sistem dapat mengirimkan notifikasi berupa e-mail kepada petani apabila nilai kelembapan tanah kurang dari batas ambang, rerata delay pemantauan node-gateway sebesar 6,01 detik, sedangkan rerata delay pemantauan gateway–server sebesar 10,02 detik, dan rerata delay pengendalian server–gateway sebesar 92,55 detik.

scholarly journals On the Need for a General REST-Security Framework

2019 ◽  
Vol 11 (3) ◽  
pp. 56 ◽  
Author(s):  
Luigi Lo Iacono ◽  
Hoai Nguyen ◽  
Peter Gorski
Keyword(s):  
Service Oriented Architecture ◽  
Cloud Services ◽  
Service Systems ◽  
Message Authentication ◽  
Security Framework ◽  
Architectural Style ◽  
Representational State Transfer ◽  
State Transfer ◽  
Service Oriented ◽  
Software Services

Contemporary software is inherently distributed. The principles guiding the design of such software have been mainly manifested by the service-oriented architecture (SOA) concept. In a SOA, applications are orchestrated by software services generally operated by distinct entities. Due to the latter fact, service security has been of importance in such systems ever since. A dominant protocol for implementing SOA-based systems is SOAP, which comes with a well-elaborated security framework. As an alternative to SOAP, the architectural style representational state transfer (REST) is gaining traction as a simple, lightweight and flexible guideline for designing distributed service systems that scale at large. This paper starts by introducing the basic constraints representing REST. Based on these foundations, the focus is afterwards drawn on the security needs of REST-based service systems. The limitations of transport-oriented protection means are emphasized and the demand for specific message-oriented safeguards is assessed. The paper then reviews the current activities in respect to REST-security and finds that the available schemes are mostly HTTP-centered and very heterogeneous. More importantly, all of the analyzed schemes contain vulnerabilities. The paper contributes a methodology on how to establish REST-security as a general security framework for protecting REST-based service systems of any kind by consistent and comprehensive protection means. First adoptions of the introduced approach are presented in relation to REST message authentication with instantiations for REST-ful HTTP (web/cloud services) and REST-ful constraint application protocol (CoAP) (internet of things (IoT) services).

Sign in / Sign up

Export Citation Format

Share Document