Shared data paths 0
Which services on nexus read the same graph over the last
6h — the coupling that decides the blast radius of a schema change.
?Two services running the same query shape depend on the same labels, properties
and indexes, whether or not they ever call each other. Change one and both are
affected. A matrix rather than a node graph because at this size a force-directed
graph is a hairball whose layout changes every render, while a matrix sorts
meaningfully and lets you read one row across.
How to read this page — shared data paths
Two services that run the same query shape depend on the same labels, properties and indexes — whether or not they ever call each other. That is the coupling that decides the blast radius of a schema or index change.
- a cell
- How many query shapes the two services on that row and column both run. Darker is more. The diagonal is left empty because a service trivially shares everything with itself.
- query shape
- A statement with its literal values stripped out, identified by Neo4j's own plan-cache hash — so the same query with different ids counts once.
- widest reach
- Shapes ordered by how many services run them. These are the statements where a changed index or a renamed property hurts most at once.
What this page will not tell you
- Who calls whom. This is not a call graph and cannot become one from stored data: nothing here carries both a trace id and a service name, so the edge "A called B" does not exist in the database. See docs/UPSTREAM-DATA.md.
- Direction or dependency. A shared shape is symmetric — it says both services read the same thing, not that one depends on the other.
docs/UPSTREAM-DATA.md. What is on this page is real and from stored data:
services that read the same shapes.
No Neo4j query shapes recorded on nexus in this window.