A polyrepo architecture splits related services or projects across separate repositories, placing each service’s environment and compose files in its own silo. Mapping the system requires finding and cloning every repository before tracing its connections. section 9.2
Treat configuration as a claim rather than a fact. Compare compose files, environment variables, application call sites, and infrastructure-as-code because development and production connections can drift, while runtime configuration and feature flags determine which edges actually run. section 9.2
Map a polyrepo architecture by checking four complementary sources:
- Compose files reveal services that boot together, such as a web app, Postgres, and Redis. section 9.2
- Environment files expose declared external dependencies, while code imports confirm integrations that configuration alone may miss. section 9.2
