Repository Pattern: how to Lazy Load? or, Should I split this Aggregate?

I have a domain model that has the concept of an Editor and a Project. An Editor owns a number of Projects, and a Project has not only an Editor owner, but also a number of Editor members. Therefore, an Editor also has a number of "joined" Projects. I am taking a DDD approach to modelling this and using the Repository pattern for persistence. However, I don't grok the pattern well enough yet to de

[tlync]

DDD の Repository パターンでは、Lazy Loading とどう向き合うかという話し。Repository のインターフェースをわりきった設計にするか、VirtualProxy みたいなパターンで対応するか、みたいな感じかな。