Dependency map

Service topology

Source-backed relationships are reconciled with Docker Compose, Eureka, Zipkin, Prometheus and Locust observations. Missing telemetry is unknown, not zero impact. Dashed arrows are startup dependencies or manual corrections.

flowchart LR
  users(["Users (Locust)"])
  subgraph app["App services"]
    api_gateway["api-gateway<br/>100% of requests, 1 instance"]
    admin_server["admin-server<br/>0% of requests, 1 instance"]
    customers_service["customers-service<br/>71% of requests, 1 instance"]
    vets_service["vets-service<br/>22% of requests, 1 instance"]
    visits_service["visits-service<br/>40% of requests, 1 instance"]
    genai_service["genai-service<br/>0% of requests, 0 instances"]
  end
  subgraph platform["Platform"]
    config_server["config-server<br/>0% of requests, 1 instance"]
    discovery_server["discovery-server<br/>0% of requests, 1 instance"]
  end
  customers_db[("customers-db<br/>embedded in customers-service")]
  visits_db[("visits-db<br/>embedded in visits-service")]
  vets_db[("vets-db<br/>embedded in vets-service")]
  users ==> api_gateway
  api_gateway -.->|"manual correction"| customers_service
  api_gateway -.->|"manual correction"| visits_service
  api_gateway -->|"list vets"| vets_service
  api_gateway -->|"genai chat"| genai_service
  discovery_server -.->|"config at startup"| config_server
  customers_service -.->|"config at startup"| config_server
  visits_service -.->|"config at startup"| config_server
  vets_service -.->|"config at startup"| config_server
  api_gateway -.->|"config at startup"| config_server
  admin_server -.->|"config at startup"| config_server
  customers_service -.->|"discovery at startup"| discovery_server
  visits_service -.->|"discovery at startup"| discovery_server
  vets_service -.->|"discovery at startup"| discovery_server
  api_gateway -.->|"discovery at startup"| discovery_server
  admin_server -.->|"discovery at startup"| discovery_server
  customers_service -.->|"inferred persistence"| customers_db
  visits_service -.->|"inferred persistence"| visits_db
  vets_service -.->|"inferred persistence"| vets_db

Services

Traffic share and restart hints help identify high-impact targets.

User actions and data flows

Connect each user-visible route to the services it needs.

Dependency semantics

Runtime calls, fallbacks, and startup requirements have different failure effects.

Potential blast radius

Qualitative predictions for a selected target, failure, and phase. Each impact includes its evidence and uncertainty.

Latest run comparison

No run for this snapshot yet.

Evidence and freshness

Review source status and manual corrections before treating a prediction as current.