domain driven design - Entity Framework Fluent API and MultiBoundedContext -


i have applied multi bounded context principle of domain driven design , have 3 different objects (in 3 different domain contexts) pointing same table in database. julie lerman suggested, have shared database model has objects. shared database model used code-first migrations. have fluent api configurations represent foreign key relationships , column constraints on shared database model. question is, should let 3 domain specific contexts know of these fluent api configurations. validate object graph in each of these contexts. should worry string lengths, required etc etc on these separate domain contexts? necessary/good practice configure these relationships on each of 3 separate domain contexts?

yes, have repeat fluent api configurations in smaller domain specific models.


Comments

Popular posts from this blog

Payment information shows nothing in one page checkout page magento -

tcpdump - How to check if server received packet (acknowledged) -