Published January 1, 2026 | Version v1

Dependency Mapping and Control-Plane Isolation for Resilient Distributed Cloud Architectures

Description

Distributed cloud services often appear redundant at the component level while sharing hidden dependencies on identity, configuration, secrets and deployment pipelines. This paper proposes a dependency-mapping method that starts from user journeys, annotates every dependency with its failure behaviour—mandatory, optional, delayed through expiry, or needed only for recovery—and separates the data plane that serves requests from the control plane that changes and restores the system. Applied to an illustrative service with 13 components and four journeys, the method shows that the identity service blocks all four journeys immediately, while configuration and secrets services block only one journey at first but three after cached leases and credentials expire. An expiry-horizon analysis shows why short outage tests miss these effects: with assumed horizons of 1, 4, 12 and 72 hours, a one-hour control-plane test reveals only the first. The method gives architects a practical way to locate shared risks and to plan continuity tests that last long enough to cross the relevant expiry horizons.

Files

ICSEMT.V14_issue4_125.pdf

Files (227.2 kB)

Name Size
md5:49453fb8d95851e2b6a6e23c41eb28b7
227.2 kB Preview Download

Additional details