This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
ArRESTed Development: Guidelines for Designing REST Frameworks
July-Aug. 2012 (vol. 16 no. 4)
pp. 26-35
Ivan Zuzak, University of Zagreb
Silvia Schreier, University of Hagen
A key challenge in developing RESTful Web systems is the lack of software development frameworks that support REST principles. This article gives practical guidelines for designing frameworks for developing such systems. Derived from intuitive formal models, these guidelines enable a development process that improves separation of concerns and the modifiability of developed systems. The authors analyze several existing Web frameworks to determine how well they correspond to these guidelines

1. R.T. Fielding, Architectural Styles and the Design of Network-based Software Architectures, doctoral dissertation, Univ. of California, Irvine, 2000.
2. C. Pautasso, O. Zimmermann, and F. Leymann, "RESTful Web Services vs. ‘Big’ Web Services: Making the Right Architectural Decision," Proc. 17th Int'l. Conf. World Wide Web, ACM, 2008, pp. 805–814.
3. S. Vinoski, "RPC and REST: Dilemma, Disruption, and Displacement," IEEE Internet Computing, vol. 12, no. 5, 2008, pp. 92–95.
4. M. Broy, "Can Practitioners Neglect Theory and Theoreticians Neglect Practice?" Computer, vol. 44, no. 10, 2011, pp. 19–24.
5. I. Zuzak, I. Budiselic, and G. Delac, "Formal Modeling of RESTful Systems Using Finite-State Machines," Web Engineering, LNCS 6757, Springer, 2011, pp. 346–360.
6. S. Schreier, "Modeling RESTful Applications," Proc. 2nd Int'l Workshop RESTful Design, ACM, 2011, pp. 15–21.
7. R.T. Fielding, "REST APIs Must Be Hypertext-Driven," blog, 20 Oct. 2008; http://roy.gbiv.com/untangled/2008rest-apis-must-be-hypertext-driven .
1. C. Pautasso, O. Zimmermann, and F. Leymann, "RESTful Web Services vs. ‘Big’ Web Services: Making the Right Architectural Decision," Proc. 17th Int'l. Conf. World Wide Web, ACM, 2008, pp. 805–814.
2. S. Vinoski, "RESTful Web Services Development Checklist," IEEE Internet Computing, vol. 12, no. 6, 2008, pp. 94–96.
3. L. Richardson and S. Ruby, RESTful Web Services, O'Reilly, 2007.
4. S. Allamaraju, RESTful Web Services Cookbook, O'Reilly, 2010.
5. R.T. Fielding, "REST APIs Must Be Hypertext-Driven," blog, 20 Oct. 2008; http://roy.gbiv.com/untangled/2008rest-apis-must-be-hypertext-driven .
6. L. Richardson, "Justice Will Take Us Millions of Intricate Moves," QCon presentation, 20 Nov. 2008; www.crummy.com/writing/speaking2008-QCon /.
7. J. Algermissen, "Classification HTTP-based APIs," 2010, www.nordsc.com/extclassification_of_http_based_apis.html .
8. I. Zuzak, I. Budiselic, and G. Delac, "Formal Modeling of RESTful Systems Using Finite-State Machines," Web Engineering, LNCS 6757, Springer, 2011, pp. 346–360.
9. S. Schreier, "Modeling RESTful Applications," Proc. 2nd Int'l Workshop RESTful Design, ACM, 2011, pp. 15–21.
10. R. Alarcón, E. Wilde, and J. Bellido, "Hypermedia-Driven RESTful Service Composition," Service-Oriented Computing, LNCS 6568, Springer, 2011, pp. 111–120.
11. J. Webber, S. Parastatidis, and I. Robinson, REST in Practice, O'Reilly, 2010.
12. S. Tilkov, "REST Litmus Test for Web Frameworks," blog, 4 Aug. 2010; www.innoq.com/blog/st/2010/07rest_litmus_test_for_web_frame.html .

Index Terms:
Media,Protocols,Web and internet services,Servers,Computer architecture,Internet,Web,Media,Protocols,Guidelines,Servers,Computer architecture,Engines,Internet,hypermedia,REST,frameworks
Citation:
Ivan Zuzak, Silvia Schreier, "ArRESTed Development: Guidelines for Designing REST Frameworks," IEEE Internet Computing, vol. 16, no. 4, pp. 26-35, July-Aug. 2012, doi:10.1109/MIC.2012.60
Usage of this product signifies your acceptance of the Terms of Use.