domain-driven-design

问题 I'm trying to implement multiple DDD bounded contexts as outlined here. This is an example context: I have an entity type configuration file for each entity with the appropriate FluentAPI mappings (reverse engineered using EF tooling). These configuration files also include the relationship configurations. e.g.: UserMap.cs // Relationships this.HasOptional(t => t.SecurityProfile) .WithMany(t => t.Users) .HasForeignKey(t => t.SecurityProfileCode); SecurityProfile and DomainPermission are not

问题 Ok So I have a PERSISTENCE layer, which grabs data from Entity Framework and puts it in some classes of its own, "Models", identical to the DB ones. PRESENTATION layer, an MVC website DOMAIN layer, which is a project independent to everything. Has some classes (Models) but not exactly as on the DB, has some business logic and so on. How do I link these 3? (references) 回答1: In a typical 3-tier Application architecture , you usually make your Data Access Layer (Data Persistence Layer if you

问题 How do you name repository and service interfaces and their implementing classes? For example I have a model with the name Question . What would you name the repository (interface and implementation) and the service (interface/implementation). After reading these posts: Java Interfaces/Implementation naming convention and Interface naming in Java I reconsidered what I already had done :) 回答1: I think that there are roughly two approaches to naming in DDD: 1) Stereotype based. This is where

问题 Example: Business rules states that the customer should get a confirmation message (email or similar) when an order has been placed. Lets say that a NewOrderRegisteredEvent is dispatched from the domain and is picked up by an event listener that sends of the confirmation message. When that is done some other event handler throws an exception or something else goes wrong and the unit of work is rolled back. We've now sent the user a confirmation message for something that was rolled back. What

问题 Taking into consideration the domain events pattern and this post , why do people recomend keeping one aggregate per transaction model ? There are good cases when one aggregate could change the state of another one . Even by removing an aggregate (or altering it's identity) will lead to altering the state of other aggregates that reference it. Some people say that keeping one transaction per aggregates help scalability (keeping one aggregate per server) . But doesn't this type of thinking

问题 I'm using asp.net mvc with entity framework and starting to learn DDD. I'm working on project that contains surveys. Here's my domain model: public class Survey { public int? SurveyID { get; set; } public string Name { get; set; } public decimal MinAcceptanceScore { get; set; } public int UserFailsCount { get; set; } public IEnumerable<SurveyQuestion> Questions { get; set; } public IEnumerable<Prize> Prizes { get; set; } public IEnumerable<SurveyAttempt> UserAttempts { get; set; } } I need

问题 I have started to look away from the normal MVC way of creating my web applications and have had a look at Domain Driven Design - DDD. From having Models alone, I now have Collections , Entities , DataMappers & Repositories in my application to work with. Full-fledged separation and modularity for sure, but now my directory structure is nothing but a complete mess! As I have never worked with a DDD-application in the past, I have little idea on how to organize my file structure. Would below

问题 I seem to have gotten myself into a bit of a confusion of this whole DDD\LinqToSql business. I am building a system using POCOS and linq to sql and I have repositories for the aggregate roots. So, for example if you had the classes Order->OrderLine you have a repository for Order but not OrderLine as Order is the root of the aggregate. The repository has the delete method for deleting the Order, but how do you delete OrderLines? You would have thought you had a method on Order called

问题 I'm stuck on finding the proper way to refer to entities located inside an aggregate root , when we only got their identities coming from URL parameters. I asked a previous question which ended up focused on value objects , so I'm starting with another example here. Let's say we want to modify an OrderLine inside an Order : The user goes to a page where he can see the Order summary along with all its Order Lines. The user clicks on the edit button next to an Order Line. He gets directed to

问题 I have a need to assign the next sequence number for a Project according to a given prefix code. So you wind up with alternate id numbers like PROJ_ABC_001, PROJ_ABC_002, PROJ_XYZ_001, PROJ_XYZ_002, etc. While this need is quite specific, I would suggest that there is a more general and common case where businesses use alternate ids that are sequential integers in order to identify different Customers, Projects, Orders - whatever. Of course these aren't primary keys in the database. And while