—In the modern era of globalization business are expanding across boundaries. This initiates a strong need to connect various business processes, people and technologies. This necessitates the need for Enterprise Integration (EI). There are various tools & technologies among them one is Web Services. These are one of the most promising and widely used technologies for developing enterprise integration solutions. One of the solutions for enterprise integration is function/method based integration and Web Services plays a major role in this area. Among various web Service architecture SOAP and REST are the most talked of and the most debatable one as well. Though both have value but generally speaking REST has always been preferred choice over SOAP among solution developers. Among experts an argument prevails as when to use each one. This paper describes the architecture of SOAP based and REST based web services and then compared both using different parameters. The aim is to help solution developers in selecting best web service considering a given scenario. The comparison parameters include many dimensions such as Coupling, Format, CRUD Operations and Network Latency. The paper also discusses an example of implementing both types of web services on middleware framework and compare results on the basis of performance with regard to both efficiency and scalability.
—Middleware framework, REST, SOAP, web services.
The authors are with Institute of Business Administration, Pakistan (e-mail: email@example.com, firstname.lastname@example.org).
Cite:Muhammad Waqas Khan and Eram Abbasi , "Differentiating Parameters for Selecting Simple Object Access Protocol (SOAP) vs. Representational State Transfer (REST) Based Architecture," Journal of Advances in Computer Networks vol. 3, no. 1, pp. 63-66, 2015.