Dependencies
The estate's internal dependency graph, coloured by health, entanglement or priority. Toggle shared data store links to see the coupling that exists without any code edge. For the kernel and ring partition, see the entanglement view; for what to cut first, see binding points.
Coupling hotspots
The most depended-on components. High fan-in is not automatically bad, but change here ripples widely, and a chokepoint without good tests is a risk multiplier.
| Component | Dependents | Tests | Runtime | Note |
|---|---|---|---|---|
| tc-connectionbroker | 126 | good | .NET Standard 2.0, .NET Framework 4.6.2, .NET Framework 4.8.1, .NET 8, .NET 10 | Well-maintained chokepoint to manage carefully |
| tc-exceptions | 77 | none | .NET Framework 4.6.2, .NET 8, .NET 10 | Chokepoint without good tests |
| backoffice-useraccount-service | 40 | some | .NET Framework 4.7.2, .NET Standard 2.0 (libraries) | Chokepoint without good tests |
| application-framework | 35 | good | .NET Framework 4.6.2-4.8.1, .NET Standard 2.0, .NET 8, .NET 10 | Binding point: pins its consumers to the legacy platform |
| tc-diagnostics-portal | 31 | good | .NET 10, nodejs | Well-maintained chokepoint to manage carefully |
| phenix-feature-service | 28 | none | .NET Framework 4.7.2, .NET Framework 4.6.2, .NET Standard 2.0 | Binding point: pins its consumers to the legacy platform |
| company-info-api | 27 | good | .NET 10, .NET Framework 4.6.2 (client packages) | Well-maintained chokepoint to manage carefully |
| mail-service | 21 | good | .NET Framework 4.7.2, .NET Standard 2.0, .NET Framework 4.6.2 | Binding point: pins its consumers to the legacy platform |
| backoffice | 18 | good | .NET Framework 4.7.2, .NET 10, .NET Standard 2.0 | Well-maintained chokepoint to manage carefully |