Domain Driven Design and Repository

Asked

Viewed 105 times

2

We are refatorando a project where initially its conception was only in CRUD, using a very simple architecture that so far worked. We were inciting some routines, we saw that what we had would not serve us. Some team members have started their studies related to Domain Driven Design and we are applying such practices.

It was decided to use Dapper Extensions (Insert and update), because we want to have control over SQL queries, since we use Sqlserver and Ravendb. For Sqlserver we want to use some tools for building Query dynamically.

What would be the best way to work with these dynamic querys, I mean, parameters, classes, etc ? As the use of DTO’s will be required.

Which of the projects will be the DTO’s classes ? Repository ? What we are thinking of doing is good practice and is valid ?

  • 3

    Yes, one has studied something and then has to apply, even if there is no need. Have you thought about it? Very few projects need DDD, and fewer will use in a way that brings more benefit than problem. But surely everyone involved will be happy to be fashionable, hopefully not the only motivation. It seems that no one understands the part of the DDD course that is not for anything. Not that I’m saying it’s not the specific case, I have no information, I’m just questioning. I think it’s a good idea to do it this way, but I’m not the best person to answer that.

  • 2

    If Maniero is not the best person to answer, all that remains is to ask God

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.