Sub-Domain with multiple bounded context and project structure -


i have started reading few chapters of blue book , have read first 3 chapters of red book (implementing domain driven design). have 2 questions:

(1) can sub-domain have more 1 bounded context? particularly looking @ example in implementing domain driven design book there forecasting sub-domain sort of coupled/overlap inventory. (apologies if have not read book, idea there strong overlap between 2 bounded contexts).

(2) how organize project solution structure (i using .net), there examples of real world projects can at? should create folders namely sub-domain, core-domain, generic-domain , specify modules under it? struggling on how best define structure shows onion/hexagonal layers in place.

thanks in advance.

  1. yes. domain composed multiple sub domains (if complex enough) , each in fact group of bounded contexts. domain can considered bounded context (bc) app point of view. bc doesn't mean contains unique model, specific representation of business concept. can have book definition in multiple bc in each, definition different, ranging full details id. book inventory different book sales example. matters how bc understands concept. resulting model valid in bc, although can have same name model bc. that's namespaces for.

  2. there isn't recipe that, structure projects how see fit. of time you'll have @ least 1 domain project , ui, persistence, infrastrcuture projects. think best structure depends on app , on how developers thinks way things might not optimum way you. in nutshell, structure app makes sense you.


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -