VegaGraph overview

One typed graph across data, software, infrastructure, operations and business meaning.

VegaGraph is the knowledge layer in Vegalake. It can describe a warehouse table and its columns, but it is not limited to a data catalog. Services, repositories, APIs, queues, Kubernetes workloads, policies, incidents, dashboards, business processes and KPIs use the same typed graph.

That common model answers questions which usually cross tools:

  • Which production services write to the table behind net retention?
  • What breaks if this repository is archived?
  • Is this column classified as PII in every environment or only in production?
  • Who owns the KPI definition, the model that computes it and the runtime that serves it?

Product model

VegaGraph stores types, entities, versioned aspects, field references and relationships as one governed workspace graph. Every assertion can retain its source, confidence, context and history, while bounded traversal keeps lineage and impact questions predictable.

Entity type ── allows ── Aspect type
     │                       │
     ▼                       ▼
  Entity ───────────── Current/versioned aspect
     │
     ├──── Field reference (column, API operation, config key)
     │
     └──── Typed edge ───────────────► Entity / field reference

Built-in views, generic core

The generic APIs expose all entity types. Friendly collection APIs expose common product views such as tables, KPIs, services, repositories and environments, including tailored 360, lineage, impact, dependency and runtime projections.

This avoids two bad extremes: a generic graph that every client has to reinvent, and a fixed catalog that cannot represent the organization it is supposed to describe.

Extensible but constrained

Vegalake ships system entity, aspect and relationship types. A workspace can add its own. Relationship contracts can restrict source and target entity categories, allow or disallow field endpoints, set cardinality, and require acyclic behavior.

VegaGraph enforces those rules on writes. Type Studio previews affected entities and relationships before an administrator publishes a change.

Next

Vegalake, VegaDB and VegaFlow are trademarks or registered trademarks of Vegalake Inc.

On this page