microservices design principles

weigh repeatedly, not only to make the structure clear, but also to achieve high cohesion and low coupling.---> Dimitri Law requires decoupling between classes, but the decoupling is limited, the principle is only for reference, if it violates this principle, the project may not fail, which requires you to use the principle of repeated measures, do not follow is not correct, strict implementation is "too bad."Iv.: Central idea(1) in a scene, the A,b,c class. Complete a goal. A relies on b,b to

Opening and closing principles Definition: A software entity such as classes, modules, and functions should be open to extensions and closed for modification. The source of the problem: in the software lifecycle, because of changes, upgrades, and maintenance, and other reasons for the software to modify the original code, may introduce errors in the old code, may also cause us to have to refactor the entire function, and the need for the original cod

Single Responsibility Principle, abbreviated as SRP.Definition: There should never is more than one reason for a class-to-change.There should be and only one cause for class changes.Division of duties? A single definition and level?should be based on actual business conditions. Focus on the point of change.In practice, classes are difficult to do with a single function, but the interface should be as single as possible.Design pattern six Principles/In

I. Design Principles1. Dependency inversion principle (DIP) High-level modules (stability) should not depend on low-level modules (changes), both of which should depend on abstraction.Abstract (stable) should not depend on implementation details (changes), and implementation details should depend on abstraction. 2. Open and closed principle (OCP) Class modules should be extensible, but cannot be modified; open to extensions and closed to changes

First Lecture: 1. Object-oriented design patterns and principles Introduction to Design Patterns: Each pattern describes a problem that recurs around us, and the core of the solution to the problem.--christopher alexander{Architect} Software designers ' understanding of the concept of design patterns: (1) The

The basis of reusable object-oriented software-design mode, with its reusable design intention, ingenious logical thinking by the vast number of object-oriented program design is sought after. But many programmers often turn the question of thinking into what patterns they encounter. This kind of confucianism、the thinking has seriously influenced the artistry of

1. Opening and closing principle (Open Close Principle)2. The principle of substitution on the Richter scale (Liskov Substitution Principle)3. Dependency reversal principle (dependence inversion Principle)4. Interface Isolation principle (Interface segregation Principle)5. Dimitri rule (Law of Demeter) and least known principle6. Single Duty principle (Responsibility Principle)7. Combination/Aggregation multiplexing principleGeneral principles of soft

What is design mode? Design patterns are a set of reusable, most known, categorized purposes, code design experience Summary. Use designPatterns are designed to reuse code, make code easier for others to understand, and ensure code reliability. There is no doubt that design patterns are more in the system than othersWi

closed principle is vague. It only describes how the objects in the software are opened for extensions, but not modified or disabled. The principle of opening and closing is an abstract summary of the first five principles. The first five principles are specific implementations of the principle. Therefore, if the principle of opening and closing is used, it is actually a bit false because it does not have

Before, the author shared an article, "Comprehensive analysis of the importance of Web page vision design principles", the article simply introduced the web design principles of the importance of visual. A friend added my QQ to discuss what principles of visual

Since the core of object design is the class, the following principles are basically the discussion of the design of the class, the other types of elements are relatively simple, basically also conforms to most of the principles listed here. Before we have analyzed the basic princi