domain-driven-design

问题 Regarding below excerpt, concerning cqrs and ddd, from Patterns, Principles, and Practices of Domain-Driven Design by Nick Tune, Scott Millett Does it mean that domain model on command side can omit most of business attributes ? How would it look like for eg Customer Entity? Could Customer entity omit FirstName, Surname etc? If so, where would these business attributes be? Only in read model in CustomerEntity? Or maybe apart from CustomerEntity containing all business attributes there would

问题 I´m trying to build a type in F#, where when I get an object of that type I can be sure it´s in a valid state. The type is called JobId and it just holds a Guid . The business rule is: It must be a Guid - but no empty Guid. I´ve already implemented the type in C# but now I would like to port it to a F# class library. That´s the C# type: public sealed class JobId { public string Value { get; } private JobId(string value) => Value = value; public static JobId Create() => new JobId(Guid.NewGuid(

问题 I´m trying to build a type in F#, where when I get an object of that type I can be sure it´s in a valid state. The type is called JobId and it just holds a Guid . The business rule is: It must be a Guid - but no empty Guid. I´ve already implemented the type in C# but now I would like to port it to a F# class library. That´s the C# type: public sealed class JobId { public string Value { get; } private JobId(string value) => Value = value; public static JobId Create() => new JobId(Guid.NewGuid(

问题 I´m trying to build a type in F#, where when I get an object of that type I can be sure it´s in a valid state. The type is called JobId and it just holds a Guid . The business rule is: It must be a Guid - but no empty Guid. I´ve already implemented the type in C# but now I would like to port it to a F# class library. That´s the C# type: public sealed class JobId { public string Value { get; } private JobId(string value) => Value = value; public static JobId Create() => new JobId(Guid.NewGuid(

问题 PRE: I've read NodeJS modules vs classes but this is more specific. As part of some refactoring in Node I have a couple of Application Services (in DDD-terminology) which are technically implemented as Node modules. Since (in a DDD-world, an probably any other for that matter) Application Services should be singletons and since Node modules are guaranteed to be 1 'instance' only, it seems to me that this is an okay fit (modules trivially implement the 'singletonness') Is there any reason why

问题 I have logic consisting of selecting a large number of records from one system, performing multiple transformations (based on business rules) and inserting them into another system. It seems like a high performance (and memory) hit to instantiate each of these records as an object, perform transformations on them and then insert all of these object into the other system. Is the best way to achieve this in DDD to skip the classes/objects and do it straight through SQL, maybe a stored procedure

问题 I am having some difficulty working out the best way to handle a fairly complex scenario. I've seen quite a few similar questions, but none addressed this scenario to my satisfaction. An Order (aggregate root) is created with multiple OrderLines (child entities). According to business rules, each OrderLine must maintain the same identity for the life of the Order. OrderLines have many (20+) properties and can be mutated fairly often before the Order is considered "locked". In addition, there

问题 I've been reading Tim McCarthy's awesome book on DDD in .NET. In his example application though, his underlying data access is using SqlCE and he's handcrafting the SQL inline. I've been playing with some patterns for leveraging Entity Framework but I've gotten stuck on how exactly to map the IRepository linq queries to the underlying data access layer. I have a concrete repository implementation called. public EFCustomerRepository : IRepository<DomainEntities.Customer> { IEnumerable

问题 most of the time in the service code I would have something like this: public SomeService : ISomeService { ISomeRepository someRepository; public Do(int id) { someRepository.Do(id); } } so it's kinda redundant so I started to use the repositories directly in the controller is this ok ? is there some architecture that is doing like this ? 回答1: You lose the ability to have business logic in between. I disagree with this one. If business logic is where it should be - in domain model, then

问题 In my application I have an assembly - MyApplication.Core which contains all of my domain objects - Customer, Order etc, as well as interfaces for repositories - ICustomerRepository, IOrderRepository I have another assembly - MyApplication.Data which contains concrete implementations of those interfaces - OrderRepository etc. The repositories are responsible for retrieving data from the DB and presenting it using the domain objects. One thing I'm not sure about is whether my domain objects