JRJoshua RandallSystems. Software. Possibility.

ENGINEERING PROJECT / PROJECT DETAILS

Infrastructure Dependency Analyzer

ENGINEERING ARTIFACT / PYTHON

Dependencies become impact.
Make the chain visible.

View source on GitHub ↗︎

The Infrastructure Dependency Analyzer traces a declared service inventory to show potential downstream business impact, dependency paths, circular prerequisites, recovery-target alignment questions, and validation order.

Explainable impact

Reverse dependency traversal identifies potentially affected services and records deterministic shortest paths that explain why each result appears.

Recovery-aware modeling

Detects cycles, highlights RTO alignment questions, and separates declared recovery objectives from demonstrated recovery capability.

Tested behavior

25 automated tests cover graph directionality, cycles, duplicate paths, malformed inventories, safe report generation, and CLI behavior. GitHub Actions runs Python 3.10 through 3.13.

EXAMPLE

Inspect the fictional construction scenario

Business-impact analysis without live discovery or production data
  • Office internet: traces six downstream services and three business workflows in the declared model.
  • ERP database: surfaces an 8-hour database RTO supporting a 4-hour application RTO as a planning review question.
  • Validation: dependency paths, prerequisite waves, owners, and cycles remain visible for review rather than being collapsed into a synthetic score.

Source code, fictional inventories, an interactive offline report, automated tests, and the CI workflow are available on GitHub.

Problem, implementation and evidence

A change can affect services through dependencies that a flat server list hides.

Model resources and directed dependency edges, then inspect the assumptions behind an impact path before using it in a change review.

What the evidence establishes

The linked project source is the implementation record. A dependency path is a hypothesis about impact until checked against the real environment.

Reproduce or extend

Compare a known service dependency with observed configuration and record stale, missing and directional edges.

Open the related experiment or review surface →

LET’S BUILD SOMETHING THAT MATTERS

Good systems start
with a conversation.

Infrastructure, engineering, technical leadership, and the next challenging problem.

Get in touch ↗︎LinkedIn ↗︎GitHub ↗︎

Explore the portfolio

Escape to close · Tab to navigate results