domain driven design quickly

"Learning Domain driven Design (ii) context map and architecture" gives you a general introduction to the concept of context mapping, and a rough introduction to the domain-driven design of the main use of architectural knowledge,

(Sequence)The greatest value of a domain model is that it provides a common language that links domain experts and technicians;(P2)A model is a form of knowledge. It simplifies the selection of knowledge and provides a purposeful structure;(P33)Object-Oriented Programming is powerful because it is based on the modeling paradigm and provides an implementation method for Model Construction;(P48)

Ddd:domain driven DesignCqrs:command Query Responsibility seperation (Command query duty separation) abbreviationQuery data in the same process as query (inquiry)Change state is called commandCRUD: (Create, Read, Update, delete) Add and deletees:event Sourcing abbreviation, event traceabilityDTO: (Data Transfer Object)When we query the data, it may be displayed on the UI, just a few attribute fields (or data) of the

written document is not updated in time, it loses its meaning, please file it. So the written document please keep as concise as possible the text and the diagram is complementary, do not deliberately biased to a certain description. The code is the most real-time and effective description of the model, but it is too biased and detailed, not to be fully understood by the domain experts, even if the domain

idempotent so that the transaction requester generates the transaction ID directly. Note: The order number is not sensitive, so you do not actually need to generate it on the server side. Or, you need an initial virtual order number that prevents "duplicates," and then the server backend can map the build itself, which is fine.This transaction ID is not actually global, if a sends a transaction request to B, and b needs to send a child transaction request to C during processing, B needs to gene

Domain-driven design methods start with modeling. They mainly include information modeling, behavior modeling, and UI modeling; Information modeling is the beginning of a domain-driven design. Information Modeling partitions info

For specific needs, please see the previous blog: DDD Domain driven design practice of how to extract the model, the following is a specific entity, aggregation, value object code, do not want to say what is the entity, aggregation and other concepts, believe that the theory of things we have known. I am curious about ddd, not in real project practice, and even d

In the domain layer, you can implement the business logic of the entity and the aggregate root, before implementing the business logic, we first determine some basic behaviors of the entity and the aggregate root, such as judging whether the entities are equal. The implementation of the specific business logic of the domain object, because it involves to interact with the database, so after the realization

(!Committed) Orderdbcontext. Value.savechanges (); Committed=true; } Public Override voidRollBack () {Committed=false; } Public Override voidDispose () {if(!Committed) Commit (); Orderdbcontext. Value.dispose (); Orderdbcontext. Dispose (); Base. Dispose (); } }}2. Then we want to implement warehousing, warehousing, mainly for object creation, reconstruction, update and destruction, which create, update and destroy through the

2015–6-28 the first chapter is the key factor of effective modeling of knowledge 1. Model and implementation of the binding model to be based on the reality of business, and the user is not the reality of the business disjointed 2. Acquiring a model-based language that describes the modeled models, such as UML diagrams, business-based terminology, without singularity, in a unified language (understood by both business and developers), means that business people and developers build a bridge of c