Replying to @stilkov
@stilkov What is canonical anyway in a world where each bounded context (or Microservice) defines its own viewpoint of a concept? #NiceRead
1
@aliostad My point exactly
Replying to @stilkov
@stilkov I love your introduction! And don't forget the typical redundancy in such models when someone lost the overview of all included.
Replying to @stilkov
@stilkov But you missed the most canonical interface: a list of key value pairs (lol)!
1
Replying to @stilkov
@stilkov so instead you opt for a lot of projections between all the different models in the different contexts?
1
Replying to @stilkov
A must read for Enterprise Architects: MT "@stilkov: “Why You Should Avoid a Canonical Data Model” innoq.com/en/blog/thoughts-o…"
Replying to @stilkov
@stilkov Some good points, also there are valid [IMHO] opposing views. Really wish this was a discussion at a venue(such as LinkedIn)