domain-driven-design

问题 I dig a lot of things about the DDD approach (Ubiquitous language, Aggregates, Repositories, etc.) and I think that, contrary to what I read a lot, entities should have behavior rather then being agnostic. All examples I see tend to present entities with virtual automatic properties and an empty constructor (protected or worst, public) and that's it. I consider this kind of objects more like DTOs then entities. I'm in the process of creating a framework with its specific API and I don't want

问题 I have a problem with Repository pattern - how to perform JOIN operations between several repositories. In this project, we use MVC, EF, DDD. I'm aware that this kind of question was here several times, I reference these questions later in this one. Between generic repository model (IRepository) and specific repository model, I chose specific option, since I consider ORM (in our case EF) as a generic repository pattern itself, so it doesn't make sense to add another generic repository and we

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed last year . Domain driven design has become my architecture of choice. I've been able to find a abundance of books & tutorials for applying DDD principles within the ASP.net framework. It mostly seems inspired from what Java developers have been doing for a good while now. For my personal

问题 Let's say I have two bounded contexts, the Shipping Context and the Billing Context . Each of these contexts need to know about the customer. At a data level, the customer is represented by a CustomerTbl table in a database. This table consists of all the necessary columns that describe the customer. Columns in CustomerTbl (simplified): Name PhysicalAddress PaymentMethod The Shipping Context is concerned with Name and PhysicalAddress while the Billing Context is concerned with Name and

问题 This question is a continuation of my previous question here zend models architecture (big thanks to Bill Karwin). I've made some reading including this article http://weierophinney.net/matthew/archives/202-Model-Infrastructure.html and this question How To Properly Create Domain using Zend Framework? Now I understand, what domain driven design is. But examples are still very simple and poor. They are based on one table and one model. Now, my question is: do they use Domain Model Design in

问题 I am quite new with DDD and would like to know about any pitfalls you might want to share. I will summarize it later for more newbies to read :) Thanks Summary so far: Anemic domain model where your entities are primarily only data bearing and contain no business logic Not using bounded contexts enough Focusing too much on patterns There is a good presentation on this topic as well here (video). 回答1: Probably the most important one: not grokking the central, fundamental principle of the

问题 Developing n-layered application with DDD (o better DDDD because we are using WCF) using Microsoft technology (where we have full controll of all component), the best choise seems to be STE vs POCO (this last one force the usage of DTOs). That's right? In your opinion make sense the usage of STE with DTOs where we need them? Thanks. 回答1: I really can recommend Julie Lerman's Programming Entity Framework. She goes in depth about simple poco's, dto's and Self Tracking Entities. Advantages and

问题 Below is a directory structure for a PHP application I have pieced together from examples that provides accessibility via a central (api.php) entry point, no namespaces yet, and class names are identical to file names . I have separated directories into authentication (has login scripts to process log in, logout, create user config (site wide settings, database settings) controllers (holds class files, with member functions that call specific data method) models (makes simple CRUD operation

问题 I have the following design : My Design My Design http://s15.postimg.org/3zha8rzqh/Design_Idea.png I will have a class called 'ProductDTO' in my service layer (the left service). When the 'Update Product ( ProductDTO )' operation contract is called - it should call the 'Update Product' function in the Business Logic Layer . In the database (the 'Data Access Layer' ) there is an entity called 'Product', and because I use LINQ-To-Entities I will also have a class there called 'Product'. My

问题 Implementing an integration with a 3rd party system which exports products and imports orders from a web site. There is some ddd work already done in the design and to continue it i would like. Should every single property on the order and products be covered with a value object? This would mean around 100 classes to cover all possible properties which seems excessive: ProductSku ProductName ProductDescription ProductPrice etc... 回答1: Should every single property on the order and products be