domain driven design for dummies

Service, leaving only the ASP. NET development server Right-click the tinylibrary. webapp project, select the set as startup project option, and press Ctrl + F5 or debug | start without debugging in Microsoft Visual Studio to start the application. After the application is started, you can see the main interface as follows: Logon account For testing purposes, tiny Library provides three user accounts by default: daxnet, acqy, and James. The username and password are as follows

I personally think that there are too many concepts in this book. The architecture and development of software are not a combination of concepts. Just use the appropriate words to describe some empirical things. The so-called risk-driven model selects the appropriate design strength based on the project situation to avoid over-design. For complex software systems

(database-driven approach ). This proves that I am in the first articleArticle"Only the domain model can be mapped to the data model, but not the data model. I can understand that many system-related friends like to consider database matters. After all, data storage is also an indispensable part of the software system (of course, the memory database should be different ), the database structure

The design principle of all-domain general architecture driven by attribute core(Abbreviation: Attribute schema principle)Contact information: 13547930387Email:[email protected]I. Personal statementI, participated in the work also has more than 5 years, is an ordinary cannot in the ordinary programmer, has been using the company own product to carry on the develo

Aggregation (Aggregate) is a very important concept in domain-driven design. Simply put, aggregation is such a set of domain objects (both entities and value objects) that combine to represent a complete realm concept. For example, according to Eric Evans's "field-driven

The core idea of domain-driven design is to focus on developersProgramThe program implementation and familiarity with domain knowledge are not considered. The design focuses on the field, and the development focuses on the model. The previous tasks were analyzed in the field

on the sales order lines, without having to deal with the sales order. Of course, you can do this, but if you have to stick to your point of view, then you are taking the sales order line as an aggregate root, that is, you acquiesced in the lines in your domain model as an entity with a separate concept. In this regard, a more "strong" view has been expressed in the community of domain-

Entity Framework, and the current Entity Framework is not completely domain-driven, preferring a technical architecture. For example, the customer entity above, in the solid frame-driven design, it has been "led by the EF" Introduction of the Statute (specification) model. In the above implementation, while LINQ make