Best practice for naming Read model tables in a CQRS architecture? -
i'm new idea of cqrs, , usual deciding how name things 1 of hardest parts of learning process.
if following convention of 1 table per view in read database cqrs application, how should go naming tables different views?
let's have number of different clients consuming read model, should name tables based on client , ui view consuming data?
is there no concern here coupling our ui read model database , webservices used performing queries? or purpose of cqrs architecture, push complexity of aggregating data read model, rather performing work in query webservices , client?
can give examples of tablenames use in denormalized read models?
or purpose of cqrs architecture, push complexity of aggregating data read model, rather performing work in query webservices , client?
yes, case. don't need worry coupling read model ui because read model built directly support ui needs.
as examples: tables reflect path specific view built for. therefore have example adminuserslist or adminproductseditprices. latter contains data web form accessible under /admin/products/edit on prices tab.
i can think of naming tables identifiers or whatever - long can resolve connection between table , view.
Comments
Post a Comment