Is it common practice to re-create database coupling rows when updating an aggregate?
Imagine we have a CRUD system with products. Each Product
can have Attributes
that represent properties of a product, like size, color, weight, etc. It’s a typical EAV database case (Entity, Attribute, Value).
Keeping it simple, the database scheme is as follows:
Is it common practice to re-create database coupling rows when updating an aggregate?
Imagine we have a CRUD system with products. Each Product
can have Attributes
that represent properties of a product, like size, color, weight, etc. It’s a typical EAV database case (Entity, Attribute, Value).
Keeping it simple, the database scheme is as follows:
Is it common practice to re-create database coupling rows when updating an aggregate?
Imagine we have a CRUD system with products. Each Product
can have Attributes
that represent properties of a product, like size, color, weight, etc. It’s a typical EAV database case (Entity, Attribute, Value).
Keeping it simple, the database scheme is as follows: