Have Geek Brain

Project architecture using DDD

Requirements
The project should contain 1 main application, and some secondary helper applications (which use the same domain objects, have some common services, but have some slightly different - unnecessary for the main application, therefore - should be separated).

Most, if not all, domain entities should have a generic search service (possibly in different DLLs), with custom search criteria and common logic to fetch possible values ​​for those criteria (e.g. sub-search for authors, get a book from it).

Problem
Does DDD fit here? And if so, what should my project structure look like? (the best format for an answer is a list of structured DLLs + some of the more significant namespaces).

0


source to share


1 answer


The idea of ​​global domain classes sounds contrary to DDD. Have you read the book?



With globally shared domain classes, there is little room for context maps. Without context maps, you get a slight advantage from DDD in all but trivial applications.

+2


source






More articles:


All Articles