Re: [ADVANCED-DOTNET] The effects of ORM in architecture and domain driven design

2008-07-21 Thread Seref Arikan
Hi Peter, Exactly the two points I have reached, after sending the post!! In fact, the Repository Pattern is very close to what I have described as my manager layer, and DDD seems to provide formalism to achive what I'd call a clean and good design. Thanks for your response. Cheers On Mon, Jul

Re: [ADVANCED-DOTNET] The effects of ORM in architecture and domain driven design

2008-07-21 Thread Peter Ritchie
I would suggest using the Repository Pattern to keep the business logic of the entities separate from the persistence logic. Domain Driven Design by Eric Evans provides some excellent information for designing domains and their interaction with the rest of the system.

[ADVANCED-DOTNET] The effects of ORM in architecture and domain driven design

2008-07-21 Thread Seref Arikan
Hi, I've just started a small web app, and I am using an ORM product for DB access, which is what I have been doing for the last 5 years. In the beginning I had my own solution, but after leaving the company I wrote it for, I did not take the code with me, and great products emerged for .NET like