domain driven design microservices architecture

The Domain-driven design ("DDD") by EricEvans is a classic concept. Although the concept of "Domain" has long existed, however, this book makes it possible for people to carefully examine the construction of software. I believe that after reading this book, you will truly appreciate the power of the field, this power d

: binding model and implementation 45Model-driven design 47Modeling paradigms and tool support 50Leader the bones show: Why models matter to users 57 . Hands-on modelers 60Part IIThe building blocks of a model-driven design 63Chapter 4: isolating the domain 67Layered

From Eric Evans wrote the classic Domain-driven design:tackling complexity in the Heart of software to this day, DDD has just developed for 10 years. It is almost the main domain design method of developing complex software system, which is not only the complement of object-oriented (component)

In fact, the infrastructure layer here is just some interface and base class of the domain layer, there are no other code such as day tools, just to illustrate some basic problems of the domain layer 1, the domain event simple implementation code, all comes to the asp.net design pattern book code Namespace DDD. Infr

What is a domain-driven design? Eric Evans, a leading modeling expert in 2004, published his most influential book: Domain-driven design:tackling Complexity in the heart of software ( Domain-

model-driven design, when we analyze such a system for users, the premise is that we have abstracted and encapsulated all the details in it, and each process can be split, finally, it can be combined to form an overall business model. Of course, this is only a technical outlook, and it is also our goal and goal. We recommend the latest Martin Fowler book: domain

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-

difficult.How the company leaders look at this way of development, most of us are in some non-professional research and development companies work, the leadership wants to see things as early as possible, it is very contradictory, need good things but not according to good things to do. If you are fortunate enough to have a research and development team for DDD, agile and XP, then you can treat the project as a lifelong artwork.These two articles are mainly some of my feelings about DDD, share

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

After we find the entity and value objects, we need to design the association between the objects.1. Associate as few as possible and not create a complex network. Complex networks are not conducive to dividing boundaries, understanding and maintaining objects, and negatively impacting performance, usually by identifying relationships that need to exist throughout the business life cycle. For example, an order item needs to be linked to a product, but

(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)

Study on the driving design of DDD Domain (ii): Warehousing repository (UP)Preface: The previous chapter introduces the aggregation division in the DDD design demo and the design of the entity and the aggregation root, which continues to say that one of the most controversial topics in DDD is the warehousing repository

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

2007 Eric Evans published "Domain driven design" so far, the concept of domain driven designs (Ddd:domain-driven design) has become increasingly understood and used. I have been a post-

In the enterprise Application architecture pattern, three kinds of domain logical organization patterns are put forward: Transaction script, domain model and table module. Many people look at the foggy, many people say the indefinitely, the main reason is not from the project level of analysis and design experience, on

Written in the front: reprint please indicate the sourceDirectory pinned: About Project--------------------WCF+EF+WPF layered framework based on DDD Domain driven design (1) Architecture--------------------WCF+EF+WPF Layered framework based on DDD Domain

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

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