domain driven design for dummies

"admin". When we model the relevant permissions, we often subconsciously put their actions in their respective roles, if the later existence of multi-role sharing behavior will be written in the abstract class using virtual method to pass down. The problem is that in the role behavior, we know that if there is a behavior then it is possible to perform irepository operations on other aggregations in the behavior, which will make the domain model messy

Unit testing best Practices for domain-driven design (ii)All along, I tried to find an effective unit test pattern, so that "unit testing" really can be popular in the team, so that unit testing is no longer a formality, but to make unit testing a way to improve the quality of the code.This article describes a scenario for implementing unit tests for

Preface In fact, this seriesArticleI have already been reposted by many netizens, And I have provided a link to the original article in my previous blog. However, after all, the popularity of the blog garden is even higher, and many netizens strongly demanded that I post the articles to the blog garden. Therefore, I finally made up my mind to reorganize and paste the series of articles in the blog garden. Based on the discussion results of netizens and their accumulation in practice, I will

1. How to extract models from DDD domain-driven design practices 2. Domain-driven design of DDD: aggregation, entity, and value object 3. DDD domain-

Domain-driven design software: the way to cope with core complexity (English version) (highly recommended by many world-class software masters) Basic Information Author: (US) Eric EvansSeries name: Turing programming SeriesPress: People's post and telecommunications PressISBN: 9787115224071Mounting time:Published on: February 1, April 2010Start: 16Other Details

The object about Domain-driven design in the software Domain-driven design is a way of thinking that aims to deal with software projects with complex problems. In the traditional waterfall software development model, it goes thro

This year, Eric Evans has groundbreaking software design books "Domain-driven design:tackling complexity in the Heart of Software" (Domain-driven design: a response to the core complexity of software) (Addis On-wesley professional

Catalog Index"Selfless sharing: ASP. NET CORE Project Combat" Catalog IndexBrief introductionIn our "selfless sharing: from beginner to proficient in ASP. NET MVC" series, we actually have ddd thinking, but not completely to achieve, because not all the good things must be used, or according to the actual situation, DDD in the large system is a very good design idea, This is not to be denied. But depending on the situation, in our small project, our

Domain-driven design: The Way to cope with software core complexity Author: Eric EvansTranslator: Chen Dafeng/Zhang zexinPress: Tsinghua University PressPublishing year: 2006-3-1Page: 390Pricing: 48.00Frame loading: 185x260ISBN: 9787302115762 Douban: http://book.douban.com/subject/1629512/Dangdang: http://product.dangdang.com/product.aspx? Product_id = 9150450 D

In 《Entityframework-Based Domain-driven design practices [continued]: Use Cases of domain-driven design practices based on EF 4.3.1 code firstIn the article, I gave a field-driven

Note: This article is author original, but can be reproduced freely.This article is purely personal point of view, Caishuxueqian, improper, please treatise.First, the field-driven designOften see everyone in the discussion of this issue, Baidu can also see a lot of related blog. In itself I have not read the relevant books, just spent some of the concepts and the like, may not really understand the concept.First, the core of

No matter whether there is software support or software is good or bad, hundreds of millions occur in every field around the world every day.UnderstandableBusiness Domain-driven design is a design method. It is hard to understand and evolve the software to solve the problem. The method used is to build a model around t

, however, warehousing is primarily used to perform read and save operations on specific persistence mechanisms/technologies. These persistence mechanisms/techniques can be an entity Framework, NHibernate, or an ADO component for a database engine. For simplicity, we centralize data access operations into warehousing and develop a specific implementation of warehousing for different persistence mechanisms/technologies, which makes it easy to maintain and deploy applications. When designing wareh

the objects within the aggregation. Warehousing (Repository) Create a repository for each aggregate root object that represents all objects of that type as a collection of conceptual objects, access to the repository through a similar set of interfaces. The point of warehousing is to let developers focus on the domain model logic and hide real data access behind the warehousing interface, which is not the