Maintaining Replicated Recovery Log for RESTful Services

2015 ◽  
Vol 7 (3) ◽  
pp. 23-35 ◽  
Author(s):  
Anna Kobusińska ◽  
Dariusz Wawrzyniak
Keyword(s):  
Information Systems ◽  
Fault Tolerance ◽  
Rollback Recovery ◽  
Failure State ◽  
Service Oriented ◽  
Restful Services ◽  
Persistent Storage

Along with development of information systems, their requirements in terms of fault-tolerance increase and become more stringent. A possible approach to deal with this issue is rollback-recovery that consists in loading by the recovering node its most recent checkpoint, or retransmitting requests saved in its message log, to reach a consistent pre-failure state. Both checkpoint and message log are commonly said to be saved in a persistent storage able to survive any failure. In this paper the authors propose the implementation of a stable storage by means of replication of the log containing recovery information. The proposed solution is especially tailored for the service oriented systems implemented accordingly to REST paradigm. Thus, they utilize RESTful semantics in order to reduce the size of replicated recovery log and thereby increasing the efficiency of the proposed recovery log replication protocol.

Applying CIM-to-PIM model transformations for the service-oriented development of information systems

2011 ◽  
Vol 53 (1) ◽  
pp. 87-105 ◽  
Author(s):  
Valeria De Castro ◽  
Esperanza Marcos ◽  
Juan Manuel Vara
Keyword(s):  
Information Systems ◽  
Model Transformations ◽  
Service Oriented

scholarly journals Selective Service Provenance in the VRESCo Runtime

2012 ◽  
pp. 372-394
Author(s):  
Anton Michlmayr ◽  
Florian Rosenberg ◽  
Philipp Leitner ◽  
Schahram Dustdar
Keyword(s):  
Performance Evaluation ◽  
Information Systems ◽  
Web Service ◽  
Scientific Workflows ◽  
Data Provenance ◽  
Provenance Information ◽  
Selective Service ◽  
Runtime Environment ◽  
Service Oriented ◽  
History Of

In general, provenance describes the origin and well-documented history of a given object. This notion has been applied in information systems, mainly to provide data provenance of scientific workflows. Similar to this, provenance in Service-oriented Computing has also focused on data provenance. However, the authors argue that in service-centric systems the origin and history of services is equally important. This paper presents an approach that addresses service provenance. The authors show how service provenance information can be collected and retrieved, and how security mechanisms guarantee integrity and access to this information, while also providing user-specific views on provenance. Finally, the paper gives a performance evaluation of the authors’ approach, which has been integrated into the VRESCo Web service runtime environment.

Service-oriented computing and model-driven development as enablers of port information systems: an integrated view

2012 ◽  
Vol 12 (1) ◽  
pp. 41-61 ◽  
Author(s):  
Maria A. Lambrou ◽  
Ørnulf Jan Rødseth ◽  
Howard Foster ◽  
Kay Fjørtoft
Keyword(s):  
Information Systems ◽  
Model Driven Development ◽  
Model Driven ◽  
Service Oriented Computing ◽  
Service Oriented

Representation of Action is a Primary Requirement in Ontologies for Interoperating Information Systems

2013 ◽  
pp. 68-76
Author(s):  
Robert M. Colomb
Keyword(s):  
Information System ◽  
Information Systems ◽  
Service Oriented Architecture ◽  
Individual Object ◽  
Significant Research ◽  
Service Oriented ◽  
Information System Engineering ◽  
Research Questions ◽  
The Individual ◽  
Rich Data

Ontologies at the present time are generally rich data models. The interoperating information system engineering paradigm Service-Oriented Architecture recognizes that the key issue in interoperating information systems is the actions performed by these systems, not so much the data. Further, the organizationally heterogeneous nature of these interoperating systems means that the individual object is difficult to characterize by classes. This chapter investigates the problems raised by giving priority in ontology representation to individuals and actions over classes, outlining a number of significant research questions in representation languages for ontologies.

A Method to Support Fault Tolerance Design in Service Oriented Computing Systems

2012 ◽  
pp. 362-376
Author(s):  
Domenico Cotroneo ◽  
Antonio Pecchia ◽  
Roberto Pietrantuono ◽  
Stefano Russo
Keyword(s):  
Fault Tolerance ◽  
Common Ground ◽  
Fault Injection ◽  
Failure Behavior ◽  
Tolerance Design ◽  
System Failure ◽  
Computing Systems ◽  
Service Oriented Computing ◽  
Service Oriented ◽  
Tailored Design

Service Oriented Computing relies on the integration of heterogeneous software technologies and infrastructures that provide developers with a common ground for composing services and producing applications flexibly. However, this approach eases software development but makes dependability a big challenge. Integrating such diverse software items raise issues that traditional testing is not able to exhaustively cope with. In this context, tolerating faults, rather than attempt to detect them solely by testing, is a more suitable solution. This paper proposes a method to support a tailored design of fault tolerance actions for the system being developed. This paper describes system failure behavior through an extensive fault injection campaign to figure out its criticalities and adopt the most appropriate countermeasures to tolerate operational faults. The proposed method is applied to two distinct SOC-enabling technologies. Results show how the achieved findings allow designers to understand the system failure behavior and plan fault tolerance.

Sign in / Sign up

Export Citation Format

Share Document