Browse Prior Art Database

Fault tolerance in an SOA environment

IP.com Disclosure Number: IPCOM000125890D
Original Publication Date: 2005-Jun-20
Included in the Prior Art Database: 2005-Jun-20
Document File: 1 page(s) / 23K

Publishing Venue

IBM

Abstract

Many speculate that some future applications will be comprised on services selected from a "service desk" -- a clearinghouse for services that perform particular functions. In some cases, fault tolerance (FT) will be supplied by the components. We disclose the introduction of a new type of SOA agreement that provides failover service only, together with the process for registering, selecting, executing and operating according to that agreement type.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 1

Fault tolerance in an SOA environment

Many speculate that some future applications will be comprised on services selected from a "service desk" -- a clearinghouse for services that perform particular functions. In some cases, fault tolerance (FT) will be supplied by the components. The component would advertise its FT properties, and applications can select appropriately. However, components fail -- even components advertised as fault tolerant. Futhermore, if the various copies of the code are the same, multiple copies of a replicated component can fail simultaneously.

In some fault-averse environments that are highly failure intolerant, the same component can be written to the same specification by separate programming teams. We'll call this a "multi-coded application" (MCA). This reduces/eliminates the simultaneous failure problem (provide the error is not a specification issue, of course), but the cost of writing such components is high.

A Service Oriented Architecture (SOA) provides the potential to gain the benefits of an MCA without requiring one company to bear the expense of writing one. We disclose the introduction of a new type of SOA agreement that provides failover service only, together with the process for registering, selecting, executing and operating according to that agreement type.

To use such a component, the following process is employed:
1. A service is written.

2. The service registers its interface, operational properties and guarantee term...