Multisite Cloud

Expose multiple distinct cloud sites as one schedulable environment while preserving site identity so placement, data movement, policy, latency, and failure-domain tradeoffs remain explicit.

Version

v2 · 2026-09-06 · History

Domain-specific #

2336

Origin domain

computer science

Subdomain

distributed cloud computing

Aliases

Multi-site cloud, Multi-datacenter cloud, Cross-site cloud

Core Idea

A multisite cloud is a cloud-computing environment composed of multiple explicitly distinguishable sites—typically data centers or regions, under one or several providers—that a user or scheduler can employ within one workload or workflow. The abstraction preserves site identity because compute capacity, data, policy, cost, latency, and failure are not uniform across the combined environment.

NIST's cloud definition supplies the shared resource, elasticity, service, and metering baseline. Multisite architecture adds a placement layer over more than one administrative or failure location.

Scope of Application

Multisite clouds support scientific workflows, disaster recovery, latency-sensitive services, regulatory placement, capacity bursting, and geographically distributed data processing. Liu and colleagues identify data placement, scheduling, provenance, reliability, and transfer as coupled concerns in data-intensive scientific workflow management. Deelman and colleagues show how workflow systems separate abstract dependencies from resource-specific execution planning.

Clarity

List sites, providers, regions, trust boundaries, identity domains, service compatibility, data residency, network topology, consistency model, placement authority, and failure assumptions. Distinguish active-active service, active-passive recovery, independent workflow task placement, and opportunistic bursting; they impose different coordination requirements.

Manages Complexity

The model makes heterogeneity schedulable. Rather than pretend resources are one uniform pool, it exposes site as a decision variable and lets the planner trade data movement against compute availability, latency, price, policy, and resilience.

Abstract Reasoning

1. Inventory site capabilities, limits, identities, and policies.
2. Map task dependencies and data locations.
3. Define hard placement constraints before optimizing preferences.
4. Estimate compute time, queue delay, transfer time, and egress cost.
5. Select placements and replication levels.
6. Establish cross-site authentication, routing, and observability.
7. Define consistency and recovery behavior under partition or loss.
8. Schedule, monitor, and re-plan as availability changes.
9. Validate that correlated dependencies do not defeat claimed site independence.

Knowledge Transfer

The portable pattern is coordinate a shared workload across multiple explicit sites without collapsing the differences that make placement consequential. It transfers to grid computing and edge–cloud systems. The proposed immediate parent is Network.

Relationships to Other Abstractions

Current abstraction Multisite Cloud Domain-specific

Parents (1) — more general patterns this builds on

• Multisite Cloud is a kind of Network Prime

  Network is the proposed immediate parent.

Hierarchy path (1) — routes to 1 parentless root

• Multisite Cloud → Network → Reservoir-Flux Network → Conservation Laws → Invariance

Neighborhood in Abstraction Space

Multisite Cloud sits in a sparse region of the domain-specific corpus (99^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

• Distributed Data Store — 0.77
• Hybrid cloud storage — 0.74
• AI Infrastructure — 0.74
• Convergence Failure — 0.73
• BCMP network — 0.73

Computed from structural-signature embeddings · 2026-09-08