SOAPatterns.org

Overview
- Introduction
- History
- Acknowledgements
- Podcasts
- Candidate Patterns
- Forms
- Press Releases
- Resources
Compound Patterns
Design Patterns (alphabetical)
Design Patterns (by category)
- Foundational Inventory Patterns
- Logical Inventory Layer Patterns
- Inventory Centralization Patterns
- Inventory Implementation Patterns
- Inventory Governance Patterns
- Foundational Service Patterns
- Service Implementation Patterns
- Service Security Patterns
- Service Contract Design Patterns
- Legacy Encapsulation Patterns
- Service Governance Patterns
- Capability Composition Patterns
  - Capability Composition
  - Capability Recomposition
- Service Messaging Patterns
- Composition Implementation Patterns
- Service Interaction Security Patterns
- Transformation Patterns
- REST-inspired Patterns
Cloud Computing Patterns
Service Technology Specs
SOA School
- Home
- Matrix
- Certifications
- Courses
- Exams
- Self-Study Kits
- Workshops
- Licensing
- Online Store

Home > Design Patterns > Redundant Implementation

Redundant Implementation (Erl)

How can the reliability and availability of a service be increased?

Problem

A service that is being actively reused introduces a potential single point of failure that may jeopardize the reliability of all compositions in which it participates if an unexpected error condition occurs.

Solution

Reusable services can be deployed via redundant implementations or with failover support.

Application

The same service implementation is redundantly deployed or supported by infrastructure with redundancy features.

Impacts

Extra governance effort is required to keep all redundant implementations in synch.

Principles

Service Autonomy

Architecture

Service

Having redundant implementations of agnostic services provides fail-over protection should any one implementation go down.

Related Patterns in This Catalog

Composition Autonomy, Dual Protocols, Entity Abstraction, Inventory Endpoint, Logic Centralization, Multi-Channel Endpoint, Service Data Replication, Utility Abstraction

Related Service-Oriented Computing Goals

Increased ROI, Reduced IT Burden

This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy, Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.servicetechbooks.com.