The Graph
The graph presents the ground thruth of the companies infrastructure assets. It shows all the relationships between different system components.
What type of problems might there be?
- The graph can grow very large, both from a database performance perspective and visualization.
- Mixing data that is manually added/maintained and automatically scanned can be hard to coordinate and visualize for users.
- Generating the graph model from the relational database requires close coordination of the schema and types. Evolving the schema will be more challenging
- Mixing of historical data (temporal graphs) and current state might be harder to reflect in the model OR at least not scalable
Measuring
What can we measure?
- avg latency for full query
- Hotspots in queries (which queries are most often used, where do we need indexes)
Users and Use Cases
- DevOps engineer examining their application components
- Red team engineer finding gaps
- Coding agents understanding the infrastructure
- Auditor validating risk and compliance on infrastructure components