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.
CQRS + Event Sourcing: (is it correct that) Commands are generally communicated point-to-point, while Domain Events are communicated through pub/sub?
I’m basically trying to wrap my head around the concept of CQRS and related concepts.
Distributed application using RabbitMQ
I am on my way to create an application with 4 bounded context using CQRS & event sourcing.
Domain Objects with Interfaces
I’m in a situation where part of my system has a dependency on another module in the same system, but the modules themselves need to remain independently deployable, where the parts they depend on would be filled in with another implementation.
Inheritance using non-abstract base class
This post is based on the question https://stackoverflow.com/questions/49002/prefer-composition-over-inheritance/11758048#comment15634305_11758048.
MVVM, DDD, and WPF Layered Application Project Structure Guidance
I am trying to setup my application’s structure in VS and I want to “try” and future proof it to a reasonable level. This application will be a WPF re-write of an old Winform app that had followed no conventions. No Layers, Tiers, Acronyms, etc…
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 ).
Is it Ok if Domain Object cross Service Boundary
Is it Ok if Domain Object cross Service-Boundary?
DDD / Layers and legacy systems
I have to refactor a complex C# app (many dialogs, mixed logic and so on).