Thanks for answering here

About your quote : “A dao is closer to the data layer, while a repository is closer to the domain.
A repository is responsible for reconstituting the aggregate root.”

This is something that is NOT in the Eric Evans book, you can try to search it there, but you wont’t find a different code rather than I posted here, because my discussion is in light of his book.

http://debasishg.blogspot.com/2007/02/domain-driven-design-inject.html

A dao is closer to the data layer, while a repository is closer to the domain.
A repository is responsible for reconstituting the aggregate root.

To quote the author of the above mentioned link:
“The methods which the DAO exposes are supposed to be fine grained ones, which need to have higher reusability. OTOH, repositories are domain artifacts and speaks the language of the domain. They provide much coarse grained contracts to the Aggregates.”

This time we did something different, because we had to develop something new and make people learn it at the same time, because we have different skills inside our team, actually our teams are a kind of cross skills team ( server-side, client-side, QA and so on mixed). So, I built a presentation about why we’re there, what we would see there, what we should achieve and so on.

The result was a proven architecture, a metrics report and a model to develop services in Python, aiming high performance and high scalability. This month we’re going to publish this documentation to the other teams, and probably make some presentations to them.

Thx for you comment !

Well, I knew all of that Actually my question was a kind of “joke” about what people have been saying about DDD and the Repository pattern itself, because people were claim something that was neither in the book, nor being practiced by the community, as I stated above, where I said that the Repository is a simply DAO like, that I’ve been using since the beginning of ages

Yes, I have to take care of this website, because I installed a skin that is not compatible with many plugins… I’ll do it soon.

As per your question, such an example would generally be based on the ActiveRecord pattern, coined and explained by Martin Fowler in his book ‘Patterns of Enterprise Application Architecture’.

I have implemented it this way myself in a Java project and I have a couple of old posts about it: http://bit.ly/7xx8zA (in portuguese) and http://bit.ly/7P0mYd

The formatting on these posts is not the best, since I changed plugins after publishing them, but you can get the idea.

Give freedom to people work is something hard to management, because most of them think they can make people more productive micromanaging everybody. But this is a big mistake, because they are paid to manage, and the techinical people “SHOULD” be paid to do the technical stuff, I mean, to solve the problem by themselves on the better way they can without being blocked by anyone else.

Ok, I was talking about responsible and professionaly qualified people, not fantasy talkers that only follow the next “wave”

But I will prepare this seminar !