Course contentsShow
← System Design
Lesson 1442 of 1,91935. Backup and Disaster RecoveryFree lesson

Dependency Mapping and Critical Path Analysis

Identify service dependencies and critical recovery sequences to prioritize restoration order during disasters.

Dependency Mapping and Critical Path Analysis

You'll learn how to identify which systems must be restored first during disaster recovery by mapping dependencies and calculating the critical path.

When disaster strikes, you can't restore everything simultaneously. Some services depend on others—your authentication service must come up before your API gateway, your database before your application servers, and so on. Dependency mapping creates a visual graph showing which services rely on which, while critical path analysis determines the optimal restoration sequence to minimize total recovery time.

Understanding Dependencies

Think of your infrastructure like a building with load-bearing walls. You can't remove them in any random order—some support others. Similarly, your payment service depends on your database, user service, and perhaps a message queue. If you bring up the payment service first, it crashes immediately because its dependencies aren't available.

Create a directed acyclic graph (DAG) where:

  • Each node represents a service or data store
  • Edges point from a service to its dependencies
  • Criticality scores indicate business impact

Critical Path Analysis

Once you've mapped dependencies, identify the critical path: the longest chain of dependent services that determines your minimum recovery time. Services on this path must be restored sequentially; anything off the path can be restored in parallel.

For example, if your critical path is: DNS → Load Balancer → Database → Auth Service → Core API (total: 45 minutes), that's your best-case RTO—even if 20 other less-critical services need restoration.

During DR execution, restore critical-path services first, then parallelize everything else. This prevents wasted effort on non-critical services while core functionality remains down.

Key Takeaway: Dependency mapping reveals what must start first, while critical path analysis shows your fastest possible recovery sequence—together they turn chaotic disaster response into an optimized, prioritized restoration plan.