Lehrstuhl Informatik 5 (Information Systems) Prof. Dr. M. 1 These presentation slides by Dominik Renzel are licensed under a Creative Commons Attribution- ShareAlike 3.0 Unported License . Today’s Top “RESTful” Services and Why They Aren’t RESTful Dominik Renzel, Patrick Schlebusch, Ralf Klamma RWTH Aachen University Advanced Community Information Systems (ACIS) Aachen, Germany renzel @ dbis.rwth-aachen.de The 13th International Conference on Web Information Systems Engineering (WISE 2012) November 28th-30th, 2012 Paphos, Cyprus.
14
Embed
Today's Top "RESTful" Services and Why They Are Not RESTful
Presentation of WISE 12 Paper "Today's Top "RESTful" Services and Why They Are Not RESTful" (Renzel, Schlebusch, Klamma)
Abstract: Since Fielding's seminal contribution on the REST architecture style in 2000, the so-called class of RESTful services has taken off to challenge previously existing Web services. Several books have since then emerged, providing a set of valuable guidelines and design principles for the development of truly RESTful services. However, today's most popular "RESTful" services adopt only few of these guidelines, resulting in overburdening developers integrating multiple services in mashup applications. In this paper we present an in-depth analysis for the top 20 RESTful services listed on programmableweb.com against 17 RESTful service design criteria found in literature. Results provide evidence that hardly any of the services claiming to be RESTful is truly RESTful, probably due to the lack of rigidness and ease-of-use of currently available decision criteria. To improve the situation, we provide recommendations for various stakeholder groups.
Full Paper: http://www.springerlink.com/index/42307200X642M240.pdf
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Lehrstuhl Informatik 5(Information Systems)
Prof. Dr. M. Jarke1 These presentation slides by Dominik Renzel are licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
Today’s Top “RESTful” Services and Why They Aren’t RESTful
Dominik Renzel, Patrick Schlebusch, Ralf KlammaRWTH Aachen University
Advanced Community Information Systems (ACIS)Aachen, Germany
Huge variety of Communities of Practice in the Long Tail Lack of custom tools for niche communities Common in Web CIS: “RESTful“ APIs as (part of) products Mash-ups become possible
But: Lack of compliance to RESTful principles Increased workload & costs for service integration Bad mash-up code quality Lower customer satisfaction (developers & end-user communities) Automatic compliance checks hardly possible Lower overall service success (community practice & provider revenue)
Study: How RESTful are today‘s top “RESTful“ services?
General Finding: “REST-smattering“– Mixed adoption of REST concepts among top services– Deliberate decisions or ongoing misconceptions– Often rather buzzword than compliance– Disadvantages for users & providers
Antidote: Increased formalization– Enables helpful tools & KPIs– Requires wide support by research & industry– Reduces complexity in service orchestration– Cure on the way from research, industry to support!