I'm in a .NET world and I mark the persistence constructors as obsolete (equivalent of @deprecared in Java), and make them non-public, e.g.: public class Thing...
Brian, I too am in a .NET world, so your solution would work for me. My only worry is that the [Obsolete] decorator will throw a Warning in the compiler, and...
We're using NHibernate which finds the obsolete constructor reflectively at runtime (long after the compiler was involved). Since our obsolete persistence...
ahhh! Cool. ORM's are good. Pretty cool approach using NHibernate....
21756
Giacomo Tesio
giacomo@...
Aug 1, 2011 5:30 pm
We have ALL entities behind pure interfaces, thus only the repository have access to the implementation classes. Our clients dll (we are on .NET too) do not...
With the valid point of redesign aside, I think that a set of guiding principles could be written about DDD from multiple different perspectives and still have...
We (also a .NET operation) use Event Sourcing. So, all aggregate data is loaded via events being replayed/applied to the aggregate. Everything is hidden...
Giacomo, So instead of your Service Layer (or in my case, the actual code-behind files) consuming your Entities, you instead make any client code access the...
One thing you can do is make these members internals (e.g. make the setting internal, but the getter is public--but see previous threads about properties)....
Hello Mike, There are *so* many "solutions" to this "problem". The fact remains that developers need to use the domain properly. The fact that persistence...
21764
Giacomo Tesio
giacomo@...
Aug 2, 2011 12:51 pm
I completely agree on the methods expressing logic (we adopt CQS<http://epic.tesio.it/doc/command_query_separation.html>to make explicit the difference between...
21765
Giacomo Tesio
giacomo@...
Aug 2, 2011 1:20 pm
... Yes, everything access the domain entities via pure interfaces: we have a bounch of IPortfolios, ICustomers and so on. (even if not all with the same...
Giacomo, Thanks so much for the reply. The architecture does sound involved, but you paint a thorough picture of how it works, and that is very helpful. Just...
Hello, I have a question about the sentence below. ... I think Model-Driven Design pattern is the most important one of patterns mentioned in DDD blue book. ...
I think that is referring to the next phase/iteration of development following the initial one. If analysis is not combined with design and development, then...
Hi, I am looking for feedbacks from people who experienced applying DDD on a WPF large apps using MVVM pattern. - What is your advices to succeed on such kind...
Riana, MVVM is an architectural pattern used in the UI/Presentation layer. To be honest there really isn't any relationship between MVVM and DDD. My guess is ...
100% agree with Dan. The objects on the WPF client should be tuned to displaying information and not (domain) objects with complex behavior. For a realistic...
Sure it helped ! In fact, it turns out that your guesses were exact. For now, I have a domain model that is used both for read and write scenarios and my...
I think no relation is between the architectural patterns, i.e. they can be used together, separately, or whatever (one does not imply the other). The Model...
Riana, On the topic of "separating reads and writes", CQRS indeed is an excellent pattern for separation of concerns (applying complex business logic vs. ...
My responses are inline ... given the fact that going this way requires a lot more infrastructures (like feeding both read and event databases and ... CQRS...
Hi Naresh and thanks for your kind reply ! I checked out your website, it is a great job and I love the idea and goal ! Keep the good work on ! I'm gonna dig...
Riana, AccountSummary is used for display only. In order to change account related information, I send very specific commands to the server (per CQS/CQRS ...
Thanks for your responses Dan, your point of veiw is more clear for me now. I'm just still wondering why is it so important to struggle and try to avoid...
Riana, I can't speak for anybody else on this forum but my personal reasons for avoiding public getters/setters is to understand that your domain model is not...
As far using or not getters/setters, your explanation make sense to me and I understand the "why" now. ... I am surprised by this theory. Does that mean that...
