Dynamic Attributes without Migrations: Graph Model and API-First Approach

Adding new fields to a database is a perennial pain point: migrations, tests, releases.

We solved this by implementing a hybrid model in PostgreSQL (graph of nodes/edges + typed attributes) combined with a self-service UI for analysts.

Key Topics:

  • Why EAV/JSONB did not work.
  • How our model achieves flexibility without sacrificing performance.
  • Self-service UI: adding a field in 2 minutes instead of 2 sprints.

Technologies

  • Recursive CTEs.
  • ACID transactions.
  • RBAC.

Who it’s for:

Developers and analysts tired of ALTER TABLE. 

Real case: 

The “Urgency Priority” field can now be added with two clicks — and is instantly available in the API. 

Outcome: 

Business gets changes in minutes; while developers focus on complex tasks. 


Flexibility without compromise — it is possible!

Comments ({{Comments.length}})
  • {{comment.AuthorFullName}}
    {{comment.AuthorInfo}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

or
Chat with us, we are online!