microservices design principles

(/*Iuserbo*/ $userBo); functionMapuser (/*Iuserbo*/ $userBo); functionAddorg (/*Iuserbo*/ $userBo,/*String*/$orgId); functionAddrole (/*Iuserbo*/ $userBo,/*String*/$roleId); } /** *business Logic (business logic), responsible for handling user behavior*/ InterfaceIuserinfoextendsiuserbo,iuserbiz{}classUserInfoImplementsiuserinfo () {}Example 2:　　　　 /** *business Object (business object), responsible for user collection and feedback of User's attribute information*/ Interfaceiuserbo{

Opening and closing principle OCP (Open for extension,closed for modification). The core idea of open and close principle is that an object is opened to expansion and closed to modification. In fact, the opening and closing principle means that changes to the class are made by adding code rather than altering the existing code. In other words, once the software developer writes out the code that can be run, it should not change it, but to ensure that it can continue to run, how to do this? Th

Design Pattern OO Principles 1, package change--single responsibility principle 2, multi-use combination, less-use inheritance-the principle of the Richter replacement 3, for interface programming, not for implementation--interface isolation principle 4, strive for loosely coupled design between interactive objects--Dimitri law 5, the class shou

Design principles:1. Single Duty principleA class, only one causes it to change. There should be only one duty. Each responsibility is an axis of change, and if a class has more than one responsibility, these responsibilities are coupled together. This can lead to fragile designs. When a duty changes, other responsibilities may be affected. In addition, multiple responsibilities are coupled together, which

is metadata? The data used to describe the environment and data, in layman terms, are configuration parameters that can be obtained from a file or from a database.-----> Develop Project Charter(1) Norm-setting, unified style programming-----> Package Changes(1) The package of changes contains two meanings: first, the same change is encapsulated in an interface or abstract class. Second: The different changes are encapsulated in different interfaces or abstract classes, and there should not be t

behavior to the superclass, to eliminate duplicate code in subclasses to achieve its advantages, provides a code reuse platform, to help the subclass to get rid of the repetition of the invariant behavior of entanglement. disadvantage : If there are too many basic methods in the parent class, the number of classes increases and the system becomes larger. application : The Templatemethod () in the AbstractClass abstract class is the template method. Command mode encapsulates a request into an o

Article Description: The designer's creativity is infinite, but the user's navigation demand is fixed, any style, as long as can meet the navigation principle several requirements, can complete the user's navigation task. The easier way is to find the page path in the page element, which is equivalent to satisfying the navigation principle. Such principles and methods can be used to test whether our design

Object-oriented design principles are at the heart of oops programming, but most of the Java programmers I've seen are enthusiastic about design patterns like Singleton (singleton), Decorator (adorner), OBSERVER (Observer), Instead of focusing enough attention on learning object-oriented analysis and design. It is impo

The open-closed principle was mentioned in the previous blog post, not in detail. This time, let's summarize some of the principles of design patterns.1 Open-closed principle: refers to the software entities (classes, modules, functions, etc.) should be able to expand, but can not be changed.The principle of understanding: the opening and closing principle is the most idealistic color of a principle, it is

reconstruction, etc.), according to the plan to do the relevant product research work, because the prophase products do not have related documents, to the work brought a lot of inconvenience. But also to the system to maximize the idea of open, in the process, seriously feel "experience" important. If you have ever used or participated in the construction of a similar system platform, that would be much better. For a time do not know how to start, a period of very distressed. But now that it's

I. Principles of text design 1. Text readability:The main function of text is to convey the author's intention and various information to the public in visual communication. To achieve this goal, we must consider the overall appeal of the text and give a clear visual impression. Therefore, the text in the design should be easy to recognize and understand, and

I read "big talk Design Patterns" and extract the principles of the design patterns mentioned in this book for future use. I. Single Responsibility Principle For a class, there should be only one reason for its change. If a class has too many responsibilities, it is equivalent to coupling these responsibilities. A change in responsibilities may weaken or suppress

Six Design Principles Single Responsibility Principle Rys replacement principle Dependency inversion principle Interface isolation principle Dimit Law Principle of opening/closing 1. Single Responsibility Principle) Single responsibility, SRP for short. The definition of a single responsibility is: there should be only one reason for class changes. The most difficult part

Design principle one : single principle of responsibility Definition: There should be only one reason for a class to cause it to change. Advantages: Reduce the complexity of the class, improve the readability of the class, improve the maintainability of the system. Example: Super Human public class Superman {public void Maintains world peace () {//Superman maintains world Peace}} Extension: public class Animal {Public void Breathe (String animal) {Sys

attribute Name: type [= default value] Visibility method Name (parameter list) [: Return value type] Examples are as follows: (3) The relationship between classes ① Association Relationship 1) bidirectional correlation. Examples are as follows: 2) One-way association. Examples are as follows: 3) Self-correlating. Examples are as follows: 4) Multiple sexual associations. Examples are as follows: 5) Aggregation relationship. Examples are as follows: 6) combined relationship. Simi

Article Description: the design and research of gesture operation used in mobile terminals are discussed. Gesture refers to a system of language that is built up by a human language center with the position and shape of the palm and finger. Gestures in handheld devices refer to the integration of a series of multi-touch events into a single event. The advantages of gesture manipulation 1. Intuition-good gesture

. NET domain driven design-first taste (one: questions, patterns, principles, tools, processes, frameworks, practices)2013-04-07 17:35:27Tags:. NET DDD Driver Design original works, allow reprint, please be sure to use hyperlinks in the form of the original source of the article, author information and this statement. Otherwise, the legal liability will be invest

Design patterns are specific applications of design principles, so the design principles in the head first design pattern are recorded below: 1 package changes.2 multi-use combination less inheritance.3 Programming for interfaces

I. Design Pattern principles: 1,Single responsibility principle: Specific description: there should be only one reason for a class change, that is, a method should do only one thing as much as possible, that is, to implement only one function as much as possible, and an interface should be responsible for only one class of function description as much as possible, the

: 1. The interface should be as small as possible (core definition ); 2. Interfaces must be highly cohesive; High Cohesion improves the capability of interfaces, classes, and modules and reduces external interactions. 3. Custom Services; Customized services provide excellent services for each individual. 4. Limited interface design; 5. Law of Demeter (dump) is also known as the least knowledge principle LKP) Definition: an object shoul