How to deal with data on the model specific to the technology being used?
There are some cases where some of the data on a class of the domain model of an application seems to be dependent on the technology being used. One example of this is the following: suppose we are building one application in .NET such that there’s the need of an Employee class. Suppose further that we are going to implement relational database, then the Employee has a primary key right? So that the classe would be something like
DDD Model to handle Localizations
I’m trying to refine my domain model for the internationalization feature, I wanted to get your input on the best approach to structuring Culture and Localization entities following Domain-Driven Design principles.
Is providing a method of a domain entity with a data/ service provider object a bad design?
I have an entity called User, and it has a method to change the user’s email address. I’m using a strongly typed object for representing the email address.
ddd enforce business rule
Am struggling to identify whenever to create new domain service or capture business rules in my domain model.
Assume we cannot assign Account to Invoice if Account IsInactive or Blocked
Aggregate Boundary repository/service design
I am trying to apply DDD to the design of a Release Management system.
Aggregate Boundary repository/service design
I am trying to apply DDD to the design of a Release Management system.
Aggregate Boundary repository/service design
I am trying to apply DDD to the design of a Release Management system.
How does one design his various architecture/business models?
I’m currently learning about various application design approaches and there’s one thing I can’t really get my head around.
How does one design his various architecture/business models?
I’m currently learning about various application design approaches and there’s one thing I can’t really get my head around.
Handling “unspecified” values in software
So I’m working on a software product where we have a number of fields that the customer can leave blank, some of which are numeric. To persist these in the database we use nullable columns. Easy peasy.