Entityframework-driven design practices: Summary

It's time to summarize this seriesArticle. I should also criticize myself. Due to my many chores and busy work, the entire series of articles had been completed on and off for more than half a year. I am very grateful for your understanding and support in the process of writing the article and asking more friends to pay attention to the field-driven design! In the following other blog posts, I will continue to discuss the practical experience of domain-driven design.

This series of articles first discusses the basic idea of field-driven design based on. net entityframework's field-driven design experience, which includes discussions on entity, value object, factory and warehouse implementation methods, and development tool features provided by entityframework, it also includes the Protocol Mode and Its.. net. We can understand from the discussion that Microsoft. net entityframework still has some shortcomings in the field-driven design support, such as support for value objects, support for entity behavior and event-driven, but we also see it. net has made great progress in DDD, including: domain specific language (DSL)-specific language Integrated Query (LINQ) object-oriented domain object models (data-oriented) and support for Composite data types. After all,. Net entityframework is a product that needs to consider the needs of a wide range of users, so it also includes some anti-DDD elements.

After discussing the entityframework practices of classic DDD, this series of articles also introduces two extended topics: Service and cqrs architecture models. Cqrs architecture pattern is DDD in recent yearsCommunityA New Practice mode of DDD is also an architecture mode discussed in the DDD community. It is based on the idea of cqs and uses event sourcing as the core. It separates the commands of the application system from the query to obtain the function of event auditing, at the same time, the system operation efficiency is greatly improved, and a wide range of space is provided for the architecture technology selection and team resource configuration. I will continue to introduce the design and implementation of cqrs in subsequent articles.

For ease of reading, relist the directories of this series of articles here. If you are interested, you can view them one by one.

• Entityframework-Domain-driven design practices-Preface
• Entityframework-driven design practices (1): From datatable to entityobject
• Entityframework-driven design practices (2): layered architecture
• Entityframework-driven design practices (III): Case study: a simple sales system
• Domain-driven design practices of entityframework (iv): storage process and reverse mode driven by domain
• Domain-driven design practices of entityframework (5): Aggregation
• Entityframework-driven design practices (6): model object lifecycle-factory
• Entityframework-driven design practices (7): model object lifecycle-warehousing
• Entityframework-driven design practices (8): Implementation of warehousing (basic)
• Entityframework-driven design practices (Part 9): Implementation of warehousing (Part 2)
• Entityframework-driven design practices (10): Specification Mode
• Entityframework-driven design practices [extended Reading]: Services)
• Domain-driven design practices of entityframework [extended Reading]: cqrs Architecture Model
• Entityframework-driven design practices: Summary

Thank you again for your attention and support for this blog!