soa principles of service design

constrained class, the next is the interface and method, it is the implementation and details of the program, and the interface isolation principle mainly constrains the interface interface, mainly for the abstract, the overall framework of the program for the construction.When using the interface isolation principle to constrain the interface, the following points should be noted: The interface is as small as possible, but there are limits. The refinement of the interface can improve

refinement of the interface can improve the design flexibility is not a fact, but if too small, it will result in an excessive number of interfaces, resulting in complex designs. So be sure to be modest. Customizing the service for an interface-dependent class exposes only the methods it needs to the calling class, and the methods it does not need are hidden. A minimal dependency can be established onl

respective rolesIn the vast majority of cases, the only thing to do is to rely instead of configuringTo build the framework--design principles carding1. COC principlesTiny framework in the design of the full consideration of this principle, usually through a certain agreement to greatly reduce the amount of configuration or development, will generally be used.

In the previous section we learned the WCF distributed development step for Win (5) service contract and Operation overloading section. Today we will continue to learn about WCF service contract inheritance and service decomposition design-related knowledge points. What are the advantages and disadvantages of WCF

WebGIS Design and Implementation Principles Dr. Hua, one of the representatives of the series 2006-2-18cheungmine1What is WebGIS?My definition is the process of requesting map data or related operations from the WWW server in the Internet field to obtain and present the map to the end user. The consensus is that the client does not need to install any plug-ins (of course, the necessary browser and XML suppo

test of malicious code. Write Tests as you write code, and then use the tests as the API provides to outside contract documents. Run these tests whenever the code changes. Don't worry about code coverage. The important thing is the external conventions. You can also consider using the contract life cycle. 8. Tiered growth Keep the API focused and then layer the new API at the top so that they can grow over time. Scalability does not imply an indefinite growth. Define the scope of the API and ex

reversal of the IOC, which is widely used in framework design. It breaks the conventional process control pattern and transfers control from the user's application code to the underlying component. There is no strict definition of control inversion, but it can be abstracted as a mechanism for managing component dependencies to ensure that components always get the right dependencies at the right time. Obviously, dependency injection is an implementat

Layer-3 switches are quite common, so I have studied the basic principles and design ideas of the layer-3 switches. I will share them with you here, hoping they will be useful to you. Based on the introduction of the three-layer switch technology and the working principle of the three-layer switch, the design of a three-layer switch is given. According to the

Some people may disagree with the order of the second and third places, because one of my friends mentioned it, but after a while, he also agreed that maintenance is more important than performance. It can only be said that it is my personal experience, and there is no way to prove the process step by step like a mathematical formula. Here we record the principles and steps that I think should be followed when doing optimization work. they are not spe

Single Responsibility Principle for Object-Oriented Design Principles (SRP) This principle was once described in the books of Tom DeMaro and Meilir Page-Jones and called it cohesion ). They define cohesion as functional correlations between components of a module. Single Responsibility Principle (SRP) Single Responsibility Principle (SRP): For a class, there should be only one reason for its change.

to enhance the robustness of the program, and maintain excellent compatibility during version upgrades. Even if a subclass is added, the original subclass can continue to run. In actual projects, each subclass corresponds to different business meanings. It is perfect to use the parent class as a parameter to pass different subclasses to complete different business logic! Summary: It looks incredible, because we will find that in our own programming, we often violate the Lee's replacement princi

principle of single responsibility.When splitting an interface according to the principle of interface isolation, you must first meet the principle of single responsibility. interface to high cohesion High cohesion is to improve the interface, class, module processing power, reduce external interaction.Specific to the interface isolation principle is to require in the interface as little as possible to publish public methods, interface is the commitment of the external, the less c

Software Design Principles-- Success, 2006-10-04 ================================== Theoretical documents: ==================================1. Define the problem.The definition of the problem is intuitive and important for software development, because no software is simply an independent service.It is necessary to develop software to better solve the problem to solve some problems. Therefore, the definiti

does not necessarily effect good, after all, business logic is not the same 5. Dimitri Law (Demeter Principle) Definition: Dimitri Law is also called the least knowledge principle, meaning that an object should have the least understanding of other objects, which should be well understood, is to reduce the coupling between the modules 6. Opening and closing principle (Open Close Principle) Definition: A software entity such as classes, modules, and functions should be open to extensions,

isolation, flexibility is poor, very inconvenient to use. According to their own system size, reasonable control interface.(2). Depending on the class selection method of the dependent interface, only expose to the calling class the method it requires, and the method it does not need is hidden. A minimal dependency can be established only by focusing on providing a customized service for a module.(3). Improve cohesion and reduce external interaction.

in the association relationship. Even if you use interfaces and abstract classes for variable type declarations, parameter type declarations, method return type declarations, and data type conversions, do not use specific classes to do these things.In most cases, open and close, the Richter substitution, rely on the reversal of three principles to appear, open and close is the target, the Richter substitution is the basis, rely on reverse is the mean

class. the input parameter in the method is called the precondition, what does it mean? We have done Web Service development should know that there is a "contract first" principle, that is, the first definition of the WSDL interface, the development of the two sides of the protocol, and then the respective implementation. The Richter substitution law also requires a contract, the parent class or interface, which is also called the

eliminate the need for the interface, it needs to refine the interface, to ensure its purity. The 2nd, in fact, is the same as the main thrust of the 1th expression, but two different descriptions of a thing.Different from the principle of single responsibilityThe above two points can be summed up as a sentence: the establishment of a dedicated interface, do not build a bloated interface, or further: interface as far as possible, the interface in the method as little as possible. Is this not th

for the interface-dependent class, exposes only to the calling class the method it requires, and the method it does not need is hidden. A minimal dependency can be established only by focusing on providing a customized service for a module.3), improve cohesion, reduce external interaction. Enable the interface to do the most things with the least amount of method.5. Dimitri rule (least known principle)Definition: An object should have minimal knowled

(Chinese + math + English)> 200 for all students whose total score is greater than 200; -- query the students whose English score is between 80 and 90. Select * from student where English> 80 and English General principles of Database Table Design In the general Java-web design, to reduce coupling, JavaBean is used as the medium for data transmission, java-be