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?