Re: Domain Driven Development

Hi Alex, I've written previously about encapsulation and Django models , and I think that's kinda relevant here. If you apply the policy "never write to a model or call .save() directly" then yes, you can ensure that the only access

Re: Domain Driven Development

Yes, and you should. Note the "domain objects" cited from the book doesn't mean "model objects". In an active record model (as in Django) it can be a bit confusing, but you should have the so called Business Objects. It is what the book calls "domain objects". They are objects that map the "pro

Re: Domain Driven Development

On 12/11/2015 9:43 AM, Alex Newman wrote: I almost hate to bring this up, but we are reading Eric Evan's book "Domain Driven Development" at my company in our technical bookclub and some techniques in the book seem to be hard to apply in DJango. The main one being the notion of aggregations:

Re: Domain Driven Development

I believe you could call a queryset this thing, or this thing a queryset On Thu, Nov 12, 2015 at 12:43 AM, Alex Newman wrote: > I almost hate to bring this up, but we are reading Eric Evan's book > "Domain Driven Development" at my company in our technical bookclub and > some techniques in the b