Architecture and resilience
Disaster Recovery Dependency Mapping
Repeatable dependency discovery across 200+ components, later reused to map six applications in less than a day.
Professional case study
200+ components
Six applications in <1 day
Reusable discovery workflow
Problem
Disaster-recovery planning needed a dependency view across more than 200 platform and application components, with evidence spread across repositories, infrastructure, and AWS cost data.
Action
Built a repeatable workflow combining repository analysis, AWS cost data, and C4/Structurizr modeling to discover and document dependencies.
Outcome
Mapped dependencies across 200+ components for disaster-recovery planning. Later reused the tooling to map dependencies for six applications in less than one day.
engineering takeaways
Reusable patterns from the work.
These notes focus on the engineering judgment, tradeoffs, and patterns behind the work.
- Combined repository evidence and AWS cost data to support dependency discovery.
- Represented dependencies with C4/Structurizr models.
- Built tooling that could be reused for subsequent application mapping.
stack
contact