Understanding the DDD Concept

Question

Good,

I’m starting a new application, relatively simple, and I want to structure it into the DDD concept.

I have read a lot on the Internet, I have seen many examples and meanings, but I would like to know more simply.

Given the following structure (the pattern I found most on the internet):

• "Project". Application: Class Library persistence/repository and interface;
• "Project". Domain: Class Library where my "Models/Entities";
• "Project".Infra.Data: Class Library responsible for mapping the models (Mapping/fluentAPI);
• ""Project. MVC: Standard MVC Project, but without Models and Directly explicit repositories;

This structure is really right? Because I intend to continue with her for my next projects and reformulate some that are already implemented.

Answer 1

The correct answer is: it depends. Your architecture must be emergent, that is, your requirements must guide the architecture.

Is this project organization correct? A: Yes.

However, what are your requirements? Very high performance? If the answer is yes, this separation of projects may affect performance, although it favors maintenance / organization.

I suggest something simpler, and if necessary, you refatora.