[雙語翻譯]計(jì)算機(jī)外文翻譯--使用軟件評(píng)估計(jì)量體系比較基于soap與rest協(xié)議的web service技術(shù)（英文）

1、Information Technology and Management Science 92 ISSN 2255-9094 (online) ISSN 2255-9086 (print) December 2016, vol. 19, pp. 92–97 doi: 10.1515/itms-2016-0017 https://www.degruyter.com/view/j/itms ©2016 Juris Tih

2、omirovs, Jānis Grabis. This is an open access article licensed under the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0), in the manner agreed with De Gruyter Open. Comparison of SOAP

3、 and REST Based Web Services Using Software Evaluation Metrics Juris Tihomirovs1, Jānis Grabis2 1, 2 Riga Technical University Abstract – The usage of Web services has recently increased. Therefore, it is important to s

4、elect right type of Web services at the project design stage. The most common implementations are based on SOAP (Simple Object Access Protocol) and REST (Representational State Transfer Protocol) styles. Maintainabili

5、ty of REST and SOAP Web services has become an important issue as popularity of Web services is increasing. Choice of the right approach is not an easy decision since it is influenced by development requirements and

6、maintenance considerations. In the present research, we present the comparison of SOAP and REST based Web services using software evaluation metrics. To achieve this aim, a systematic literature review will be made

7、to compare REST and SOAP Web services in terms of the software evaluation metrics. Keywords – Literature review, REST, SOAP, Web services. I. INTRODUCTION A. Problem Formulation Nowadays the most common way to exchange

8、 data among information systems is to use Web services. Web services are self-contained, modular and dynamic applications by their nature [1]. Most common implementations are based on SOAP (Simple Object Access Protoc

9、ol) and REST (Representational State Transfer Protocol) styles. Each of these approaches has its own advantages and disadvantages, so it is important to choose the right type of Web services, otherwise it can lead to

10、certain problems in data exchange or impose some restrictions. This paper compares SOAP and REST approaches to give recommendations on how to opt the right Web service type at a project design phase. There are a numb

11、er of related studies on these protocols, primary benefits and final value [2], [3], [4]. Other articles review real implementation examples [5], [6]. This research paper summarises these studies and gives a comparison

12、, which helps identify the key differences and benefits of SOAP and REST protocols. B. Aim and Tasks The aim of the paper is to summarise the main SOAP and REST protocol advantages and disadvantages. To achieve this ai

13、m, the following tasks are set: (1) to define the metrics by which it is possible to mutually compare SOAP and REST protocols; (2) to compare SOAP and REST by found metrics; (3) to evaluate which protocol type is be

14、tter on the basis of software evaluation metrics. II. THEORETICAL BASIS This section addresses the key concepts that will be used in the paper. A. Web Services A single Web service consists of service and service descri

15、ption where service is a software module offered by a service provider, which is available through the Web. A service description contains the details of the service interface and implementations, including data types

16、, metadata, categorisation information and the location where the service is exposed [3], [1]. Service description is published in the service registry, where services are displayed and grouped by their purpose. A w

17、eb service is the key element in the integration of different information systems, as information systems can be based on different platforms, programming languages and technologies. B. SOAP SOAP compared to REST is an

18、 older protocol, which was developed as an alternative to CORBA (Common Object Request Broker Architecture) standard. To ensure data transport in SOAP, protocols such as HTTP, SMTP, etc., are used, while the data are

19、sent in XML format [3]. The main principle of this approach is as follows: a service provider publishes a service description or interface to the service registry, so the service requester can find a right service in

20、stance and use it [7]. The amount of data sent by SOAP can cause some performance problems because when forming the message SOAP adds an additional header and body parts to the message. SOAP-based Web services include

21、a variety of standards, such as WSDL, WSBPEL, WS-Security, WS-Addressing (responsible for the Web service and message addressing) [8]. These standards were developed by standardisation organisations, such as W

22、3C and OASIS. C. REST REST is a newer approach, which uses the HTTP protocol to transmit data, while the data are formed by XML, JSON, etc. formats [3]. It simplifies access to Web services by using the existing and we

23、ll-known standards instead of adding a new data processing layers on the transmission and communication stack [9]. Thus, REST tends to be a lighter alternative to the heavy SOAP protocol. REST Web services are based o

24、n self-defining resources where the HTTP protocol is used to reach them. A service is provided as a resource that can be identified by URI (Uniform Resource Identifier) [8]. For example, if URI http://www.example.co

25、m/rest/user/1 is opened in the Web Information Technology and Management Science _______________________________________________________________________________________________ 2016/19 94 C. Data Synthesis The search st

26、ring was executed in the digital libraries andafter that the study selection was extracted in an Excel spreadsheet. The following details were included about the study: title, authors, publication year, publication for

27、m (journal/ conference/etc.) and abstract. First selection round was based on the “title and abstract” of the study, where the study was categorised as follows: (I) relevant, (II) irrelevant and (III) moderate. Artic

28、les in the moderate category were reviewed in full with the result that they were either included or not included in the relevant studies group. This step resulted in 122 studies. In the next step, articles were evalua

29、ted based on inclusion and exclusion criteria, which resulted in 14 primary studies. The review process can be summarised by four main steps: Step 1: Creating a search string, executing search string in the digital libr

30、aries and saving the results into the Excel spreadsheet; Step 2: The result relevance is rated based on the titles and abstracts. This step also includes the duplicate checking; Step 3: The inclusion and exclusion crite

31、ria are applied; Step 4: This step covers the article analysis and after that the conclusions are made. Figure 1 shows the review process with a number of articles. Fig. 1. The review process with a number of studies.

32、IV. COMPARISON METHODIn the context of software development, there are direct and indirect metrics [2]. These metrics will be taken as the basis for the comparison method. These direct and indirect metrics will be used

33、 to point out the key principles that should be taken into the account when selecting between SOAP or REST approaches. A. Cost REST is based on a simple technological infrastructure,where the service can be developed

34、with minimal development tool usage. It automatically reduces the cost that would be needed to achieve the same result with the SOAP approach [4]. In addition, it is possible to work without REST client at the beginni

35、ng of the development or testing phases, as access to the REST service can be ensured directly from the Web browser by accessing the resource address. B. Effort In order to reduce maintenance costs when developing andp

36、ublishing Web services on the Web, it is advised to use the REST approach. In turn, if there is a need to use any other Web services to reduce maintenance costs, the recommendation would be to use a SOAP WSDL approach

37、 [2]. C. Lines of Code A recent study [2] compared SOAP with REST to find outhow many lines of code are needed to ensure the same functionality. In order to develop a REST service, there were 4016 lines of code written

38、. In turn, to develop a SOAP service, there were 3844 lines of code written. Accordingly, in order to implement the REST client, there were 1117 lines of code written, and to realise SOAP client there were 509 lines o

39、f code written. D. Execution Speed Web service execution speed can be objectively measured byresponse time when a Web service returns a response to the client. Response time comparison between SOAP and REST approaches

40、 was made by the University of North Florida [8]: A SOAP client makes a request to the SOAP service, where it selects or adds data to the database, depending on the type of request. As a result, the response time from

41、 service was measured. In the same way, requests through the REST service were made. The experiment resulted in a conclusion that REST showed shorter response times and better data throughput than the SOAP protocol.

42、In [11] it is marked out that SOAP is not suitable in cases of slow data transfer speed or the network has a large load. In [10] a response time measurement experiment was made by simulating a simple client-server scenar

43、io: (1) create a user, (2) user saves a message, (3) a request is made to query user’s messages and (4) delete a user. The experimental results show that the SOAP-XML service processing time is 4–5 times higher compared

44、 to the REST approach (Fig. 2).Fig. 2. REST and SOAP response time measurements [10]. Initial selection of studies - identify relevant studies Selection based on titles and abstracts Selection based on inclusion and e