Tag Info

New answers tagged

4

You need to understand that DDD is not about primary keys, rows or tables - these are just means to implement it. Aggregate root is usually implemented as a class, because you are expected to access all the functionality and data of the aggregate through the root. It therefore needs to have some behavior, something which primary key of the table can't have. ...


2

If Employee is an aggregate root, it means that all the outside objects can reference only the Employee (and not the ActiveEmployee/InactiveEmployee). Any references from outside the aggregate should only go to the aggregate root. DDD aggregate by Martin Fowler I don't think that's your intent. I think ActiveEmployee and InactiveEmployee are both ...


0

The key issue here is, how is business logic invoked transparently when a REST call is made? This is a problem that is not directly addressed by REST. I have solved this by creating my own data management layer over a persistence provider such as JPA. Using a meta model with custom annotations, we can invoke the appropriate business logic when the entity ...


1

I think you are treading on dangerous ground here. On one hand you have an LDAP authentication system which also has user name, and extra info in it. On the other you have a domain concept of a product owner. Its tempting to see the LDAP service as just a repository for product owners, but I dont think it really is. you will have all sorts of users in AD, ...


1

I have done some more research in domain driven development. Bounded Contexts seemed to help me solve this problem. I started modeling out the system and not caring about the persistence, as you should do with DDD. In the infrastructure level, I have separated out where data should be saved. The data that is related to the User and Organisation for ...


0

The answer i've seen most often is to add : public object MetaData To the class. Obviously this provides plenty of flexibility, but no type saftey. Another option would be to add a GUID Id to all 'entity' style classes. This would allow consuming classes to implement thier own store of metadata keyed off the Id


1

First of all I would like to object "correctness by DDD". Domain Driven Design is all about constructing model of domain and exposing it in your design using object-oriented programming. It is not a set of strict rules, rather list of guidelines and patterns. I assume that both types (Obj1 and Obj2) stored in the map are meaningful to domain. Otherwise this ...



Top 50 recent answers are included