Dependency Matrix¶

Service-to-service dependency table showing which services call which, and over what protocol.

Reading the Matrix¶

• Each row is a calling service (source)
• Each column shows the protocol used: REST (synchronous HTTPS) or Kafka (asynchronous event)
• Services are grouped by domain

Outbound Dependencies (Who Does This Service Call?)¶

Booking¶

svc-reservations calls:

External¶

svc-partner-integrations calls:

Guest Identity¶

svc-guest-profiles calls:

Guide Management¶

svc-guide-management — No outbound service dependencies

Logistics¶

svc-gear-inventory calls:

svc-transport-logistics calls:

Operations¶

svc-check-in calls:

svc-scheduling-orchestrator calls:

Product Catalog¶

svc-trail-management calls:

svc-trip-catalog — No outbound service dependencies

Safety¶

svc-emergency-response calls:

svc-safety-compliance calls:

svc-wildlife-tracking calls:

Support¶

svc-analytics — No outbound service dependencies

svc-inventory-procurement calls:

svc-location-services — No outbound service dependencies

svc-loyalty-rewards calls:

svc-media-gallery calls:

svc-notifications — No outbound service dependencies

svc-payments calls:

svc-reviews calls:

svc-weather calls:

Coupling Analysis¶

Highest Fan-In (Most Depended Upon)¶

Services with the most inbound dependencies — changes to these services have the widest blast radius.

Highest Fan-Out (Most Dependencies)¶

Services with the most outbound calls — these services are most affected by changes elsewhere.

Data Source¶

Generated from architecture/calm/novatrek-topology.json by portal/scripts/generate-topology-pages.py.