microservices design principles

First, the overall design pattern is divided into three main categories :Create five types of models: Factory method mode, abstract Factory mode, singleton mode, builder mode, prototype mode.structure mode , a total of seven kinds: Adapter mode, adorner mode, proxy mode, appearance mode, bridging mode, combined mode, enjoy the meta-mode.There are 11 types of behavioral patterns : Strategy mode, template method mode, observer mode, iteration sub-mode,

preset default state should have some commonality and intelligence, and help or hint at user actions, and leave the user with the ability to modify and set the default state; icon, multimedia design, detail design and additional function design to enhance experience and improve experience; Visual design, such as

Sharing (six principles of object-oriented design model) and six design models I recently read an article titled "Please call me your first brother" on the six principles of the design mode. It is simple, easy to understand and can't help but repost and share it with me !!

flexible, and the object function can be changed dynamically.4. Reduce the coupling relationship between objects. Minimize the coupling between objects and make objects independent as much as possible.5. Open and Close principles. Modifications to classes are closed and extensions to classes are open.6. Dependency on high-level abstraction. Do not rely on specific implementations.7. single class responsibility principle. In the course of designing a

Introduction to the six principles of object-oriented design and six major object-oriented design In fact, they all complement each other. That is to say, some principles must be used to implement themselves. The six principles are as follows: 1) A single responsibility p

absolutely necessary for the documentation of SQL expressions; 5 Define the standard object naming conventions. 2, table and field design　　 1) Table Design principles (1) standardization and normalization; The standardization of data helps to eliminate data redundancy in the database. There are several forms of standardization, but third normal Form (3NF) is of

Design principles include: 1. Single responsibility principle, 2. Lee's replacement principle, 3. Dependency inversion principle, 4. Interface isolation principle, 5. The dimit law, 6. Open and Close principles. 1. Single Responsibility PrincipleSingle Responsibility Principle, SRP ): There shoshould never be more than one reason for a class to change. For a cl

In all the revolutions that have taken place in the software industry, two factions were once so widely rooted in the hearts of the people, structured programming and object-oriented programming. All mainstream modernProgramming LanguageBoth of them are under intense influence. In fact, if you don't want to write it like structured and object-oriented programmingProgramIt is a hard task. None of our mainstream programming languages are Goto, so they are subject to the most important prohibitions

As we all know, design principles are the cornerstone of design patterns. When the design principles are followed, the written code becomes very flexible and can cope with changes and be easier to maintain. Of course, it is not so absolute. Next, we will briefly introduce so

submodule or business logic;Through the business logic compression interface in the public method, the interface often to review, as far as possible to get the interface to "flesh", rather than "fat doodle" a lot of methods;has been contaminated with the interface, as far as possible to modify, if the risk of a large change, the use of adapter mode for conversion processing;Understand the environment and refuse to follow blindly. Each project or product has specific environmental factors, don't

. Dependency inversion principle: high-level modules do not depend on low-layer modules, both of which are dependent on abstraction. Or just the example: Duck is a high-rise module, Fly is a low-level module. Duck does not depend on fly, the high-rise module changes slowly, while the lower-level modules change slowly.Abstractions should not be dependent on implementation details, and implementation details should be dependent on abstraction. Fly is an abstraction, it does not depend on how to fl

1. Overview Dr. Roy Fielding (see Personal homepage) is the main designer of the HTTP and URI protocol issued by the IETF. HTTP and Uri are the two most important web infrastructure protocols, so Dr. Fielding is one of the founders of the Web architecture. In addition to academic excellence, Dr. Fielding has been involved in the design and development of many Open-source software. He was the developer of Libwww-perl, one of the world's earliest HTTP

The so-called No recruit wins a recruit, practice a kung fu divides into internal strength and drilling.Drilling is like the moves, is the so-called 23 kinds of design patterns. But the internal strength, is the heart, that is the 6 kinds of laws. Light will drilling that is huaquanxiutui, the internal strength is the situation.So many design patterns, learned 2 times. 3 times you'll probably forget just th

priority design, the case is mainly for picture design, but the concept of "average law" should be applied to product design, user experience, information architecture--almost any other area of design. Let's look at product design and mobile priority

The typical object-oriented principles can be divided into two categories: class-oriented and package-oriented.Class-oriented includes: srp--single responsibility principle.ocp--Open closure principle.LSP--The principle of the Richter replacement.dip--dependency Inversion principle.isp--interface Isolation principle.Package-oriented include: The emphasis is on the cohesion of the package design requirements

both the order table and the Order record table, the order table read and write frequently, and the order record table for the management, read and write general) 7, Configuration table, log table, scheduled task table, etc. 8. Summary table Design (Multi-Table association queries will be slow, but also easy to get stuck in the case, you can consider a summary of the business, record to the summary table)Fourth step in optimization designAfter the pr

independent of the customers who use it.5. Advantages and DisadvantagesPros: Scalability is good. When we add a new module to the export, do not need to change the original code, only need to add a new import and export behavior class, and then the client side by setting the different behavior to determine the different import and export results.Cons: Increase in codeTherefore, judging the use of design patterns of standards, I think, is the function

(' Myctrl ', function () {});④ using the Controller:Ngcontroller directive: ng-controller= "Myctrl";⑤ in the controller's callback function, the $scope object is injected, specifying the model data: $scope. variable = value;⑥ Display:{{}}--ng directive:$scope scope control objects to connect model data to views;Initialize Data--nginit:$scope object;⑦ directive:Ng-click, Ng-dbclick, Ng-focus, Ng-blur;⑧ Note:Define model data, must inject $scope;In order to identify the variables and methods decl

cause changes in the interface. Visible view changes visible view is the interface provided to customers, such as JSP programs, swing interface, and so on, this part of the change in general can cause a ripple effect. The basic path of a project should be this: project development, refactoring, testing, commissioning, operation, the reconstruction of which can modify the original design and code, operation and maintenance to minimize the original cod

"/"; return NewChu ($a,$b); Break; Case"%"; return NewQuyu ($a,$b); Break; } } } $j= Gongchang::d uixiang (3,2, "%");//Test Echo $j->js ();//OutputOutput resultsSecond, the design of six major principles1. The open-close principle is that the design should have good support for the extension, and the modification should be strictly limited.2. On the Richter scale also, the subclass mu