Network Diagram

Pro

Clusters solved from the graph Laplacian, not settled by a simulation.

Layout

Service traffic at peak

Requests per second between eighteen services

storefrontcatalogauthsearchmetricscheckoutcartsessionslogsmediainventorypricingtracingprofilespaymentsalertsfraud
18 nodes, 32 links1 name has nowhere to sit and is in the tooltip only

The gateway carries the most traffic at 2,140 requests per second. The observability services form a cluster of their own, joined to the rest by four thin links. Arrow keys walk the nodes from the most connected to the least, Enter pins one and its links, Escape clears it. Nodes can be dragged. On a keyboard, Shift with an arrow key moves the selected node eight pixels, and Backspace returns it to where the layout put it. Every link follows as a table.

Service call graph, eighteen services and thirty-two links
LinkFromToreq/s
gateway to storefrontgatewaystorefront900
gateway to searchgatewaysearch640
gateway to authgatewayauth520
gateway to metricsgatewaymetrics80
storefront to catalogstorefrontcatalog480
storefront to cartstorefrontcart310
storefront to mediastorefrontmedia260
storefront to authstorefrontauth200
cart to checkoutcartcheckout190
cart to inventorycartinventory120
checkout to paymentscheckoutpayments170
checkout to fraudcheckoutfraud150
checkout to inventorycheckoutinventory110
checkout to authcheckoutauth130
payments to fraudpaymentsfraud90
payments to logspaymentslogs60
catalog to pricingcatalogpricing300
catalog to mediacatalogmedia240
catalog to inventorycataloginventory210
catalog to logscataloglogs40
search to catalogsearchcatalog420
search to pricingsearchpricing160
search to metricssearchmetrics50
auth to sessionsauthsessions480
auth to profilesauthprofiles260
sessions to profilessessionsprofiles140
inventory to metricsinventorymetrics35
metrics to logsmetricslogs300
metrics to alertsmetricsalerts220
metrics to tracingmetricstracing140
logs to tracinglogstracing180
alerts to tracingalertstracing90

Neither layout is a simulation. Clusters are the two eigenvectors of the normalised graph Laplacian just above the trivial one, which is the exact answer to the problem a spring layout approaches by shaking. Nobody told it about the four groups in the legend of your head; it separated them from the traffic numbers alone. Hops is a breadth-first tree with each subtree given a wedge worth its leaf count. Both land on the same pixels every run. Drag any node to pull it clear, or hold Shift and use the arrow keys: two services sitting on top of each other means the layout found their neighbourhoods near identical, and it is still you who has to read it. A moved node keeps a dashed outline and the link underneath puts everything back, so what the layout said is never lost. On hops, a node slides around its own ring and no further, because there the radius is the number of hops and dragging across rings would be editing the data rather than the view.

This component installs from the private registry, which opens with Pro. The command and the one-time setup are shown here once your licence key is in this browser.

6 sections, and every other premium component

The preview above is the real Network Diagram, running. One purchase opens the sections above on this page and on every other component in the library.