Graph Diagram Transitions for Data Model Evolution
Model data model evolution with graph transitions. Document current schemas, interim states, and target entity relationships.
Data models evolve as systems grow. Entities are added, relationships change, and schemas are refactored. NeoArc Studio's Transitions feature for graph diagrams models these planned states, allowing you to document current entity relationships, interim schemas, and target data architectures.
Use Cases for Graph Transitions
Database Schema Migration
Current schema → Interim schema (backward compatible) → Target schema. Plan multi-step database migrations.
Microservices Decomposition
Monolith data model → Strangler Fig phase → Service-owned databases. Document the data ownership transition.
Entity Refactoring
Track entity splits, merges, and relationship changes. Before: Customer. After: Account + Contact.
API Versioning
Document data model changes across API versions. v1 schema, v2 additions, v3 deprecations.
Creating a Graph Transition
Graph-Specific Transition Benefits
File Storage Structure
Graph transitions are stored as separate files alongside the main graph diagram.
data-model.graph-diagram.json
graph-transitions/
current-state.graph-diagram.transition.json
phase-1-normalise.graph-diagram.transition.json
target-schema.graph-diagram.transition.jsonTransition Status
| Status | Meaning | Example |
|---|---|---|
| Planned | Future schema not yet started | Target: Microservices Data Model |
| In Progress | Currently being implemented | Phase 1: Extract User Service DB |
| Completed | Migration finished | Legacy: Monolith Schema (reference) |
| Deprecated | No longer relevant | Abandoned: NoSQL Experiment |
Example: Service Decomposition
The data-architecture examples include a complete microservices decomposition scenario with three transitions showing the evolution from monolith to distributed data ownership.
Comparing Transitions
Use transitions to facilitate discussion and decision-making.