Restful web services vs. "big"' web services: making the right architectural decision

ABSTRACT

Recent technology trends in the Web Services (WS) domain indicate that a solution eliminating the presumed complexity of the WS-* standards may be in sight: advocates of REpresentational State Transfer (REST) have come to believe that their ideas explaining why the World Wide Web works are just as applicable to solve enterprise application integration problems and to simplify the plumbing required to build service-oriented architectures. In this paper we objectify the WS-* vs. REST debate by giving a quantitative technical comparison based on architectural principles and decisions. We show that the two approaches differ in the number of architectural decisions that must be made and in the number of available alternatives. This discrepancy between freedom-from-choice and freedom-of-choice explains the complexity difference perceived. However, we also show that there are significant differences in the consequences of certain decisions in terms of resulting development and maintenance costs. Our comparison helps technical decision makers to assess the two integration styles and technologies more objectively and select the one that best fits their needs: REST is well suited for basic, ad hoc integration scenarios, WS-* is more flexible and addresses advanced quality of service requirements commonly occurring in enterprise computing.

REFERENCES

• 1: G. Alonso, F. Casati, H. Kuno, and V. Machiraju. Web Services: Concepts, Architectures, Applications. Springer, 2004.
• 2: Apache. Axis2. http://ws.apache.org/axis2/.
• 3: Paul Clements , Rick Kazman, Software Architecture in Practices, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2003
• 4: T. Berners-Lee. Cool URIs don't change, 1998. http://www.w3.org/Provider/Style/URI.html.
• 5: T. Berners-Lee, R. Fielding, and L. Masinter. Uniform Resource Identifier (URI): generic syntax. IETF RFC 3986, January 2005.
• 6: Andrew D. Birrell , Bruce Jay Nelson, Implementing remote procedure calls, ACM Transactions on Computer Systems (TOCS), v.2 n.1, p.39-59, February 1984 [doi>10.1145/2080.357392]
• 7: Christoph Bussler, B2b Integration, Springer-Verlag New York, Inc., Secaucus, NJ, 2003
• 8: William R. Cook , Janel Barfield, Web Services versus Distributed Objects: A Case Study of Performance and Interface Design, Proceedings of the IEEE International Conference on Web Services, p.419-426, September 18-22, 2006 [doi>10.1109/ICWS.2006.145]
• 9: F. P. Coyle. XML, Web Services, and the Data Revolution. Addison-Wesley, May 2002.
• 10: D. Crockford. JSON: The fat-free alternative to XML. In Proc. of XML 2006, Boston, USA, December 2006. http://www.json.org/fatfree.html.
• 11: Eclipse. Web Tools Platform (WTP) Project. http://www.eclipse.org/webtools/.
• 12: Roy Thomas Fielding , Richard N. Taylor, Architectural styles and the design of network-based software architectures, University of California, Irvine, 2000
• 13: R. Fielding. waka: A replacement for HTTP. In APACHECON US 2002, November 2002. http://www.apache.org/~fielding/waka/.
• 14: R. Fielding. A little REST and Relaxation. The International Conference on Java Technology (JAZOON07), Zurich, Switzerland, June 2007. http://www.parleys.com/display/PARLEYS/A\%20little\%20REST\%20and\%20Relaxation.
• 15: Daniela Florescu , Andreas Grünhagen , Donald Kossmann, XL: an XML programming language for web service specification and composition, Proceedings of the 11th international conference on World Wide Web, May 07-11, 2002, Honolulu, Hawaii, USA [doi>10.1145/511446.511456]
• 16: K. Gottschalk, S. Graham, H. Kreger, and J. Snell. Introduction to web services architecture. IBM Systems Journal, 41(2):170--177, 2002.
• 17: H. Haas. Reconciling Web services and REST services (Keynote Address). In Proc. of the 3rd IEEE European Conference on Web Services (ECOWS 2005), Växjö, Sweden, November 2005.
• 18: J. Hadley. Web Application Description Language (WADL), 2006. http://wadl.dev.java.net/.
• 19: D. Hansson. Keynote. In Canada on Rails, January 2006.
• 20: Gregor Hohpe , Bobby Woolf, Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2003
• 21: IETF. HTTP, 1999. http://www.ietf.org/rfc/rfc2616.
• 22: E. Landre and H. Wesenberg. Rest versus soap: as architectural style for web services. In 5th International OOPSLA Workshop on SOA & Web services Best Practices, 2007.
• 23: K. Laskey, P. L. Hègaret, and E. Newcomer, editors. Workshop on Web of Services for Enterprise Computing. W3C, February 2007. http://www.w3.org/2007/01/wos-ec-program.html.
• 24: Bertrand Meyer, Applying "Design by Contract", Computer, v.25 n.10, p.40-51, October 1992 [doi>10.1109/2.161279]
• 25: Richard Monson-Haefel, J2EE Web Services, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2003
• 26: J. Nielsen. URI as UI, March 1999. http://www.useit.com/alertbox/990321.html.
• 27: OASIS. Organization for the Advancement of Structured Information Standards. http://www.oasis-open.org/.
• 28: OASIS. Web Services Resources Framework (WSRF 1.2), April 2006. http://www.oasis-open.org/committees/wsrf/.
• 29: OASIS. Web Services Business Process Execution Language, April 2007. http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.pdf.
• 30: H. Overdick. Towards resource-oriented bpel. In 2nd ECOWS Workshop on Emerging Web Services Technology, November 2007.
• 31: C. Pautasso and G. Alonso. The JOpera visual composition language. Journal of Visual Languages and Computing (JVLC), 16(1-2):119--152, 2005.
• 32: Programmable Web. API Dashboard, 2007. http://www.programmableweb.com/apis.
• 33: L. Richardson and S. Ruby. RESTful Web Services. O'Reilly, May 2007.
• 34: P. Seebach. Making URLs accessible, June 2001. http://www.ibm.com/developerworks/library/us-cranky8.html.
• 35: Roger Sessions, Fuzzy boundaries: objects, components, and web services, Queue, v.2 n.9, December/January 2004-2005 [doi>10.1145/1039511.1039533]
• 36: J. Snell. Resource-oriented vs. activity-oriented Web services. IBM developerWorks, October 2004. http://www-128.ibm.com/developerworks/webservices/library/ws-restvsoap/.
• 37: Toshiro Takase , Keishi Tajima, Efficient Web Services Message Exchange by SOAP Bundling Framework, Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference, p.63, October 15-19, 2007
• 38: S. Todd, F. Parr, and M. Conner. A Primer for HTTPR, July 2001. http://www.ibm.com/developerworks/webservices/library/ws-phtt/.
• 39: Jeff Tyree , Art Akerman, Architecture Decisions: Demystifying Architecture, IEEE Software, v.22 n.2, p.19-27, March 2005 [doi>10.1109/MS.2005.27]
• 40: Steve Vinoski, Serendipitous Reuse, IEEE Internet Computing, v.12 n.1, p.84-87, January 2008 [doi>10.1109/MIC.2008.20]
• 41: Steve Vinoski, Web Services Interaction Models, Part 1: Current Practice, IEEE Internet Computing, v.6 n.3, p.89-91, May 2002 [doi>10.1109/MIC.2002.1003137]
• 42: Steve Vinoski, Putting the "Web" into Web Services: Interaction Models, Part 2, IEEE Internet Computing, v.6 n.4, p.90-92, July 2002 [doi>10.1109/MIC.2002.1020331]
• 43: Werner Vogels, Web Services Are Not Distributed Objects, IEEE Internet Computing, v.7 n.6, p.59-66, November 2003 [doi>10.1109/MIC.2003.1250585]
• 44: W3C. Web Services Addressing, May 2006. http://www.w3.org/2002/ws/addr/.
• 45: Sanjiva Weerawarana , Francisco Curbera , Frank Leymann , Tony Storey , Donald F. Ferguson, Web Services Platform Architecture: SOAP, WSDL, WS-Policy, WS-Addressing, WS-BPEL, WS-Reliable Messaging and More, Prentice Hall PTR, Upper Saddle River, NJ, 2005
• 46: Christian Werner , Carsten Buschmann , Tobias Jacker, Enhanced Transport Bindings for Efficient SOAP Messaging, Proceedings of the IEEE International Conference on Web Services, p.193-200, July 11-15, 2005 [doi>10.1109/ICWS.2005.53]
• 47: WS-I. Web Services Interoperability. http://www.ws-i.org.
• 48: Jin Yu , Boualem Benatallah , Regis Saint-Paul , Fabio Casati , Florian Daniel , Maristella Matera, A framework for rapid integration of presentation components, Proceedings of the 16th international conference on World Wide Web, May 08-12, 2007, Banff, Alberta, Canada [doi>10.1145/1242572.1242697]
• 49: A. Zarras. A comparison for middleware infrastructures. Journal of Object Technology, 3(5):103--123, May-June 2004.
• 50: Olaf Zimmermann , Mark R. Tomlinson , Stefan Peuser, Perspectives on Web Services: Applying SOAP, WSDL, and UDDI to Real-World Projects, Springer-Verlag New York, Inc., Secaucus, NJ, 2003
• 51: O. Zimmermann, J. Grundler, S. Tai, and F. Leymann. Architectural decisions and patterns for transactional worlflows in SOA. In Proc. of the 5th International Conference on Service-Oriented Computing, Vienna, Austria, 2007.
• 52: O. Zimmermann, T. Gschwind, J. Kuester, F. Leymann, and N. Schuster. Reusable architectural decision models for enterprise application development. In Quality of Software Architecture (QoSA) 2007, Boston, USA, July 2007.
• 53: O. Zimmermann, J. Koehler, and F. Leymann. Architectural decision models as micro-methodology for service-oriented analysis and design. In SEMSOA Workshop, Hannover, Germany, May 2007.
• 54: Olaf Zimmermann , Sven Milinski , Michael Craes , Frank Oellermann, Second generation web services-oriented architecture in production in the finance industry, Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications, October 24-28, 2004, Vancouver, BC, CANADA [doi>10.1145/1028664.1028772]
• 55: Michael zur Muehlen , Jeffrey V. Nickerson , Keith D. Swenson, Developing web services choreography standards: the case of REST vs. SOAP, Decision Support Systems, v.40 n.1, p.9-29, July 2005 [doi>10.1016/j.dss.2004.04.008]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.12 Interoperability

Additional Classification:
  A. General Literature
  A.1 INTRODUCTORY AND SURVEY

  C. Computer Systems Organization
  C.2 COMPUTER-COMMUNICATION NETWORKS
      C.2.2 Network Protocols

  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures

  H. Information Systems
  H.1 MODELS AND PRINCIPLES

General Terms:
Design, Standardization

Keywords:
HTTP, REST, SOAP, WS-* vs. REST, WSDL, architectural decision modeling, resource oriented architectures, service oriented architectures, technology comparison, web services