Abstract
SummaryThe popular Representational State Transfer (REST) architectural style for constructing web applications offers simplicity and scalability advantages. However, to improve the survivability of a RESTful application, programmers commonly find themselves writing vast amounts of nontrivial, ad hoc fault tolerance code. Network volatility, HTTP server errors, service outages—all require custom fault handling code, whose effective implementation requires considerable programming expertise and effort. These implementation impediments hinder the survivability of RESTful applications—without proper fault tolerance functionality, these applications are likely to crash when experiencing faults. To provide a systematic and principled approach to handling faults in RESTful applications, this article presents FT‐REST—an architectural framework for specifying fault tolerance functionality declaratively and then translating these specifications into platform‐specific code. FT‐REST encapsulates fault tolerance strategies in XML‐based specifications and compiles them to modules that reify the requisite fault tolerance. To validate our approach, we have applied FT‐REST to enhance several realistic RESTful applications to withstand the faults described in their FT‐REST specifications. As REST is said to apply verbs (HTTP commands) to nouns (URIs), FT‐REST enhances this conceptual model with adverbs that render REST reliable via reusable and extensible fault tolerance. Copyright © 2014 John Wiley & Sons, Ltd.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
More From: Concurrency and Computation: Practice and Experience
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.