domain driven design microservices architecture

1. How to extract models from DDD domain-driven design practices 2. Domain-driven design of DDD: aggregation, entity, and value object In fact, the infrastructure layer mentioned here is only some interfaces and basic classes of t

This article is the second part of a two-part article that discusses how to use TDD to write tests before writing code and to create better designs through this process. In the 1th part, I wrote a version of the complete number finder using the Post test development method (writing the test after writing the code). Then, use TDD (write the tests before you write the code, so you can write another version with the design of the test driver code). At th

A common kind of agile development practice is TDD. TDD is a pattern of writing software that uses tests to help you understand the final steps of the requirements phase. Write the test first, then write the code, which will consolidate your understanding of what the code needs to do. Most developers think that the main benefit of TDD is the resulting integrated unit test set. However, if executed correctly, TDD can improve the overall design of the

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

) {using (var connection = getconnection ()) {connection. Open (); Connection. Insert (New {AccountId = index. AccountId, AccountName = index. AccountName}, constants.accountindextable); } }Private SqlConnection getconnection () {return new SqlConnection (configsettings.connectionstring); } }}From the above we can know that it uses the data access technology is dapper, not EF, it also has no IQueryable design

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-

Before we introduce an instance, we need to review and learn more about layered architecture. "Layer" is a kind of architecture pattern [POSA1], and is one of the most widely used and flexible models by software practitioners. Remember on the CSDN, often have a friend asked: "What is stratification?" Why should I be layered? Is the three-tier architecture the pre

Unit testing best Practices for domain-driven design (i)After introducing the DDD case, we can finally get to the topic, the test code of this program is based on Xunit, the assertion component is fluentassertions, and similar components have shouldly. In addition, this case uses code contracts for. NET, and if this plugin is not installed, individual tests may n

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