Non-Disruptive Service Relocation (Erl, Naserpour)
How can cloud service activity be temporarily or permanently relocated without causing service interruption?
ProblemThere 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.
SolutionA 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.
ApplicationVirtualization technology is used by the system to enable the duplication and migration of the cloud service implementation across different locations in realtime.
MechanismsCloud Storage Device, Cloud Usage Monitor, Hypervisor, Pay-Per-Use Monitor, Resource Replication, SLA Management System, SLA Monitor, Virtual Server
Compound PatternsBurst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Elastic Environment, Infrastructure-as-a-Service (IaaS), Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Software-as-a-Service (SaaS)
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 2).
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: