Geek Answers Handbook

Domain Modeling, Domain Objects in DDD

I am really new to DDD and trying to understand some of the concepts.

Can someone explain to me the idea of ​​domain modeling in DDD.

I already explained Wikipedia: http://en.wikipedia.org/wiki/Domain_model , but still it seems that in my understanding there are gray areas.

Based on what I understood, domain modeling involves building a model around business units to express your relationships, express the entities that participate in the model, etc.

Wasn’t this always the case in practice? in an object-oriented world, you model business objects into classes, objects, etc. and create software around it.

What I don't understand is that Domain Modeling is accessing DDD. Is it the same object / class modeling that you find in the OO world, or is it something new for DDD? How is it different from object oriented design / modeling?

Your answers are highly appreciated.

+5
source share
2 answers

One of the differences is that the “correct” implementation of the Domain Model Model in DDD is isolated from cross-cutting issues.

For example, it contains nothing to do with databases or other persistence. Where it contains the validation logic, this is a business audit, not "does the name exceed the length of the column?" check.

, "" - ( " " ), , "", .

, " " IO, UI .., - .

, . -, , , ( 1:1 , ).

+6

DDD OO. , OO, , , , .

( , ). . , , , , (, , , , ). , , , . , Facade Observer.

+1

More articles:


All Articles