Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Web Systems and Algorithms Application Integration Styles Application Integration Styles What are the application integration styles mentioned in the paper? Which are appropriate for REST or SOAP? What are the application integration styles mentioned in the paper? Which are appropriate for REST or SOAP? Shared database Discussion of REST vs SOAP File transfer Chris Brooks RPC Department of Computer Science Message Bus University of San Francisco Department of Computer Science — University of San Francisco – p.1/?? Strengths of SOAP According to the authors, what are some strengths of SOAP? Department of Computer Science — University of San Francisco – p.4/?? Department of Computer Science — University of San Francisco – p.2/?? Strengths of SOAP Protocol transparency/independence Service interface allows: abstraction from underlying protocol and serialization details machine-readable description synchronous and asynchronous message patterns tools hide complexity from users Department of Computer Science — University of San Francisco – p.5/?? Department of Computer Science — University of San Fra Weaknesses of SOAP According to the authors, what are some weaknesses o SOAP? Department of Computer Science — University of San Fra Weaknesses of SOAP Easy to misuse. Data leakage, interoperability issues. Implementation issues. Strengths of REST According to the authors, what are some strengths of REST? Possible to express types in XML Schema not representable with WSDL Strengths of REST Simple - leverages existing standards. Pervasive infrastructure. Use of port 80 Low barrier for adoption Possible to discover resources without a central repository Highly scalable Department of Computer Science — University of San Francisco – p.8/?? Department of Computer Science — University of San Francisco – p.7/?? Weaknesses of REST According to the authors, what are some weaknesses of REST? Weaknesses of REST Department of Computer Science — University of San Fra Transport Layers Not all “verbs” supported by all servers/proxies How do REST and SOAP differ in their use of HTTP? GET has data transfer limitations Why is this an issue? Challenging to encode data structures in a URI Department of Computer Science — University of San Francisco – p.10/?? Department of Computer Science — University of San Francisco – p.11/?? Department of Computer Science — University of San Fran Heterogeneity What sorts of heterogeneity can REST and SOAP handle? Department of Computer Science — University of San Francisco – p.13/?? Contracting The authors refer to contract-first programming and contract-last programming. What does this mean? Loose Coupling Loose Coupling What do the authors mean by loose coupling? Time/Availaibility What sorts of loose coupling are supported by SOAP and REST? Location Service Evolution Department of Computer Science — University of San Francisco – p.14/?? Department of Computer Science — University of San Fran Abstractions What design choices are required when building a RESTful web service? Abstractions What design choices are required when building a RESTful web service? Resource identification URI design Interaction semantics Resouece relationships Data representations Department of Computer Science — University of San Francisco – p.16/?? Department of Computer Science — University of San Francisco – p.17/?? Department of Computer Science — University of San Fran Abstractions What design choices are required when building a SOAP-based web service? Abstractions What design choices are required when building a SOAP-based web service? Data Representation What choices of data representation are available when using REST or SOAP? Data modeling Message exchange patterns service operation enumeration Department of Computer Science — University of San Francisco – p.19/?? Service Description How can services be described using REST or SOAP? Department of Computer Science — University of San Fran Department of Computer Science — University of San Francisco – p.20/?? Reliability Reliability How can we achieve reliability with either REST or SOAP? How can we achieve reliability with either REST or SOAP? Properties of reliability: AtLeastOnce, AtMostOnce, ExactlyOnce, InOrder Department of Computer Science — University of San Francisco – p.22/?? Department of Computer Science — University of San Francisco – p.23/?? Department of Computer Science — University of San Fran Security Security How can we achieve security with either REST or SOAP? Department of Computer Science — University of San Francisco – p.25/?? REST use cases What are some situations where REST would be a good design choice? Department of Computer Science — University of San Francisco – p.28/?? Transactions How can we achieve security with either REST or SOAP? How can we achieve transactional semantics with either REST or SOAP? Signing, encryption, attachment of certificates, non-repudiation ACID properties. Department of Computer Science — University of San Francisco – p.26/?? SOAP use cases What are some situations where SOAP would be a good design choice? Department of Computer Science — University of San Francisco – p.29/?? Department of Computer Science — University of San Fran