Are Persistence-Ignorant objects able to implement lazy loading?

Persistence Ignorance is an application of single responsibility principle, which in practice means that Domain Objects (DO) shouldn’t contain code related to persistence, instead they should only contain domain logic.

Justification for bidirectional relationship

I typically try and avoid bidirectional relationships at all costs. Recently I’ve been trying to follow a more domain centric design philosophy and I’m looking for advice in the best way to solve a specific problem.

Are factors such as Intellisense support and strong typing enough to justify the use of an ‘Anaemic Domain Model’?

It’s easy to accept that objects should be used in all layers except a layer nominated as a data layer. However, it’s just as easy to end-up with an ‘anaemic domain model’ that is just an object representation of data with no real functionality ( http://martinfowler.com/bliki/AnemicDomainModel.html ).

Resources for popular domain models [closed]

Closed 10 years ago.

Accessing Repositories from Domain

Say we have a task logging system, when a task is logged, the user specifies a category and the task defaults to a status of ‘Outstanding’. Assume in this instance that Category and Status have to be implemented as entities. Normally I would do this:

Should a domain expert make class diagrams?

The domain expert in our team uses UML class diagrams to model the domain model.

Can the following Domain Entity contain logic for creating/deleting other entities?

a) As far as I understand it, in most cases Domain Model DM doesn’t contain code for creating/deleting domain entities, but instead it is the job of layers ( ie service layer or UI layer ) on top of DM to create/delete domain entities?

Sample domain model for online store

We are a group of 4 software development students currently studying at the Cape Peninsula University of Technology. Currently, we are tasked with developing a web application that functions as a online store. We decided to do the back-end in Java while making use of Google Guice for persistence(which is mostly irrelevant for my question). The general idea so far to use PHP to create the website.

DDD Model Design and Repository Persistence Performance Considerations

So I have been reading about DDD for some time and trying to figure out the best approach on several issues.

Should I use structure from a core library graphic toolkit in my domain?

In java (and many other programming language), there are often structure to deal with graphic element : Colour, Shape, etc. Those are most often in a UI toolkit and thus have a relatively strong coupling with UI element.