Service Map Example

Service Map Example An architecture diagram generated by Archify. Ingress Controller · Production namespace Ingress Controller Frontend · RPS 1000 · P99 50ms · Production namespace Frontend RPS 1000 · P99 50ms API Gateway · RPS 800 · P99 100ms · Production namespace API Gateway RPS 800 · P99 100ms User Service · RPS 500 · P99 80ms · Production namespace User Service RPS 500 · P99 80ms Order Service · RPS 300 · P99 120ms · Production namespace Order Service RPS 300 · P99 120ms Redis · Production namespace Redis PostgreSQL · shared database · Production namespace PostgreSQL shared database Payment Service · RPS 100 · P99 200ms · Production namespace Payment Service RPS 100 · P99 200ms Kafka · Production namespace Kafka HTTP Production namespace Legend Frontend Backend Database Message bus

How the dependencies are extracted

  • • Collect flows with hubble observe --namespace production -o json
  • • Aggregate source/destination k8s:app= label pairs with sort | uniq -c to build the dependency graph

Reading the figures

  • • RPS comes from hubble_http_requests_total and P99 from hubble_http_request_duration_seconds_bucket
  • • Order Service is the widest fan-out point, branching into PostgreSQL, Kafka, and the Payment Service