we are design a project in Onion Architecture.

I read in various articles about the differences between dao(Data Access O and repository. In fact, we saw the structure of my project required to use Dao because our Repository would engage us in ddd like Aggregate. Now, in your opinion, is it true that We use dao instead of the Repository in our project Because our structure is data driven and in onion structure. in blow link differences between dao and repository: https://stackoverflow.com/questions/19935773/dao-repositories-and-services-in-ddd

In projects with a data driven approach(not ddd approach), is the use of the Repository correct? Because the repository has rules that may not be accurate in data driven projects, for example, the Repository per aggregate concept.

In general, I mean, do you think it's not enough to use dao in data driven projects?

  • 1
    I think you need to do a more detailed description of your problem. Someone could try to answer the generic answer in your title, but this may not match the real problem you're currently facing. – Walfrat Aug 20 '18 at 6:55
  • @Walfrat Please read again. I completed my question thanks – amirhamini Aug 20 '18 at 7:39

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.