Home > Design Patterns > Non-Disruptive Service Relocation
Non-Disruptive Service Relocation

Non-Disruptive Service Relocation (Erl, Naserpour)

How can cloud service activity be temporarily or permanently relocated without causing service interruption?

Problem

There are circumstances under which redirecting cloud service activity or relocating an entire cloud service implementation is required or preferable. However, diverting service activity or relocating a cloud service implementation can cause outage, thereby disrupting the availability of the cloud service.

Solution

A system can be established whereby cloud service redirection or relocation is carried out at runtime by temporarily creating a duplicate implementation before the original implementation is deactivated or removed.

Application

Virtualization technology is used by the system to enable the duplication and migration of the cloud service implementation across different locations in realtime.
Non-Disruptive Service Relocation: An example of a scaling-based application of the Non-Disruptive Service Relocation pattern (Part 1).

An example of a scaling-based application of the Non-Disruptive Service Relocation pattern (Part 1).

Non-Disruptive Service Relocation: An example of a scaling-based application of the Non-Disruptive Service Relocation pattern (Part 2).

An example of a scaling-based application of the Non-Disruptive Service Relocation pattern (Part 2).

Non-Disruptive Service Relocation: An example of a scaling-based application of the Non-Disruptive Service Relocation pattern (Part 3).

An example of a scaling-based application of the Non-Disruptive Service Relocation pattern (Part 3).

NIST Reference Architecture Mapping

This pattern relates to the highlighted parts of the NIST reference architecture, as follows:

Non-Disruptive Service Relocation: NIST Reference Architecture Mapping
Non-Disruptive Service Relocation: NIST Reference Architecture Mapping