433 reputation
29
bio website twitter.com/SystematicFrank
location Munich, Germany
age
visits member for 3 years, 3 months
seen Feb 10 at 7:38

Software Engineer/Programmer/Developer and all that applies ;-)


Feb
5
asked Design of a custom query result array with lazy loading
Jan
4
comment Is depending on lazy loading a code smell?
Just a few days later and I have run into a situation where I am so relieved I forced myself to reference entities just by ID and avoid hiding a query with lazy loading. While lazy-loading stops the load of a huge nested data set into memory, it makes easier running into the problem of serializing an Entity into a huge document (like JSON for a web interface) and having to 'rethink' one extra model to export my data outside my Domain layer.
Jan
4
accepted Is depending on lazy loading a code smell?
Dec
28
asked Is depending on lazy loading a code smell?
Dec
15
answered What language to use for prototyping and creating quick scripts?
Nov
1
awarded  Tumbleweed
Jul
19
awarded  Commentator
Jul
19
accepted Complex fetching of Domain Objects
Jul
19
comment Complex fetching of Domain Objects
mmm... just reading my previous comment I realized that ProjectRepository::getTasks(project) is not so bad. I refused the idea of a plain query like that because I was thinking in a "tree like" access ... however now I am thinking about an enhanced query object that provides such tree like access abstraction with the persistance layer. Never saw a tree result Query class, but that might fit the bill. Time to research again. Thanks for the inspiration
Jul
19
comment Complex fetching of Domain Objects
I would love to manage Task objects through an aggregate with Project as root. However it's my understanding that aggregates should be pulled all at once. Whenever I see danger of an Entity pulling out too many associations, I split the aggregate. Still I want a class that given one single Project, it takes care of fetching/adding and cascading the deletions. Sounds like a repo, but ProjectRepo and TaskRepo serve other type of queries. Sounds like an aggregate, but then, aggregates should be repo agnostic. Right? Hence I try to cheat the golden rules with a Service emulating an Aggregate
Jul
19
comment Complex fetching of Domain Objects
I believe that there are common DDD solutions to this problem without lazy loading. Looking back at my own code in previous projects, I realize that lazy loading was most of the time a comfortable way to ignore architecture problems. I do not wan to give up so soon
Jul
19
revised Complex fetching of Domain Objects
deleted 35 characters in body
Jul
19
asked Complex fetching of Domain Objects
May
3
awarded  Scholar
May
3
accepted Unique Value Object vs Entity
May
3
comment Unique Value Object vs Entity
Interesting... as a side effect of understanding better this difference, now I can clearly see the importance of stateless/inmutable value objects in order to improve my programs stability. I guess I was thinking too much about GUI implementation details... easy mutation is nice in the Application Layer, but in the Domain Layer I do want the AdvertisementEvent to be inmutable!
May
3
comment Unique Value Object vs Entity
Thanks so much! Despite reading so many times about asking that question to differentiate Entities from Value Objects, this time it has finally "clicked". I guess I needed a problem in my real life to learn that lesson. I love my problem because it exposed en Event Object (which is not a Domain Event) and what seems to be uniqueness (which is an invariant). I guess that in my question I should have said "invariant" instead of "transactional integrity rule".
May
3
awarded  Yearling
May
3
asked Unique Value Object vs Entity
Jan
15
awarded  Yearling