Hi, I agree with this completely. I tried using TDD as many (superb) authors sell it, where as you drive to testing you decouple like mad to allow you to test...
This all makes sense and I always find it funny to read Agile books that talk about YAGNI and avoiding unnecessary complexity and then proceed to complicate...
... Well, maybe I don't get you, but if you don't care for a distinction between implicit and published interfaces, given that using abstract classes carries ...
... between implicit and published interfaces, ... be in your opinion the difference between ... No, I agree that there definitely is a difference between...
... but I do think TDD and unit testing is essential. OK - carried away a bit there ;-). I just mean that I have known people to go to extreme lengths to unit...
I just want to express my opinion about that (SOA and DDD). I view SOA simply as the way to "integrate" systems (subsystems or even perhaps "bounded contexts")...
Hi all, I just joined this forum and I'm enjoying reading the messages. It's kind of funny to see that many of you have asked the same questions I have asked...
Hi All, I've got a question, essentially I want to know how you recommend dealing with cross-aggregate validation. For example lets say Customer is the root of...
Hi Colin, ... I feel it is a programming error if interface layers are coded to allow association of an Account with the wrong type of Customer, or to attempt ...
First off thanks for replying and providing such good information. We have an approach similiar to what you suggest for state changes, for example you can ask...
I don't suppose I could define SOA. Anyone has his own favorite view. But let's look at what SOA tries to solve. The top two in my list: - Integrate systems...
In our system, Customers can make requests for products that are not in stock, and an email will be sent to them when a restock event happens. We have a...
Nothing wrong with a design that feeld like ER. My personal guideline is that for any part of a system that is light on business logic and heavy on data...
Another option is to denormalize customer_name to productrequest table, if that's the only column you'll need from productrequest in the foreseeable future. -...
Appologies if I've missed something but is this sort of situation not also covered by the discussion of using an object in one aggregate to create part of...
We have this sort of situation and we resolve it by having seperate classes that are specifically designed to get the information needed to display in lists. ...
Thanks for the link, I have found it useful. I would like to hear what other DDDers out there think of this approach. In our case we are still trying to work...
Related to our question is where to put the behaviour to kick-start the generation of a product request. One thinking is to ask the product to Restock for a...
Our previous post was helpful, and we hope to try for more information with a different examples. Theres an ecommerce website, and customers make orders. For...
Hi, Just a kind of trivial question I've been wondering about. If I have a domain object, say User, which has an image associated with it, am I letting...
I'm having a similar issue with my domain. I have a object called Original which is a reference to a scanned document. In my case, I see it as part of the...
Hi, Is the image part of the domain or is the image's filename part of the domain? I would imagine the image is part of the domain and the filename is a...
Good thoughts, colleagues. It is a delicate issue in DDD indeed. A lot of aggregates have a kind of relationships to other aggregates, e.g. Customer's address...
Under this solution is LookupEntity an abstract class from which all lookup Name/Value type classes inherit? I like having a seperate class for each lookup...
Actually, LookupEntity is an interface. The actual implementation normally extends a base class derived from a StringAssociation (SimpleLookupEntity) or an...
My worries about joins isn't regarding populating the initial lookup entity, but as it relates to a domain object. In the case of Rainbow when fetching it from...
No -- my mistake. We never keep references to LookupEntities in domain objects. We keep a reference to the code, then provide a getter that returns the...
How do you all deal with collections of objects? I find very often that I have situations where I have to maintain a collection, but need to control what goes...
