Architecture Tools

Microservice Service Map

Paste a service configuration manifest, explore an interactive dependency graph, and surface the relationships between domains, owners, and protocols.

Configuration

Provide services and dependencies. Use status to colour nodes.

{
  "services": [
    {
      "id": "gateway",
      "domain": "Edge",
      "owner": "Platform",
      "status": "healthy",
      "description": "Entry point routing traffic to downstream services."
    },
    {
      "id": "auth",
      "domain": "Security",
      "owner": "Identity",
      "status": "healthy",
      "description": "OAuth and token validation service."
    },
    {
      "id": "user-profile",
      "domain": "Core",
      "owner": "Accounts",
      "status": "warning",
      "description": "CRUD operations for user metadata."
    },
    {
      "id": "notifications",
      "domain": "Engagement",
      "owner": "Messaging",
      "status": "healthy",
      "description": "Email and push notification pipeline."
    },
    {
      "id": "payments",
      "domain": "Billing",
      "owner": "Finance",
      "status": "critical",
      "description": "Payment gateway integration and ledger service."
    }
  ],
  "dependencies": [
    { "source": "gateway", "target": "auth", "protocol": "REST" },
    { "source": "gateway", "target": "user-profile", "protocol": "REST" },
    { "source": "auth", "target": "user-profile", "protocol": "gRPC" },
    { "source": "user-profile", "target": "notifications", "protocol": "Kafka" },
    { "source": "user-profile", "target": "payments", "protocol": "REST" },
    { "source": "payments", "target": "notifications", "protocol": "SQS" }
  ]
}

Graph controls

Adjust link visibility and highlight a service to inspect connected edges.

Link opacity

Use mouse drag to pan, scroll to zoom, and click a service node to focus it.

Service catalogue

Valid JSON config required to show services.

Dependency map

Interactive force-directed graph rendered with D3.

Tips for actionable maps

• Keep service IDs unique—they serve as node identifiers in the graph.

• Link metadata (protocols, notes) appears on the edge labels—use abbreviations for readability.

• Colour coding is controlled via status. Choose from healthy, warning, or critical.

Roadmap

• Coming soon: import directly from OpenAPI/AsyncAPI specs or service catalogues.

• Export snapshots as SVG or PNG to drop into architecture docs and post-incident reviews.

• Add edge weighting to visualise request throughput or latency budgets on each dependency.