This page
Business Services Analysis Business Services User Interface Processing Concept Application Structure Application Summary
Business service
In a service-based architecture, the application consists of a more basic service that is processed by the processing service (see processing) and the business function and user interface (UI).
When analyzing the business service, you will see that its architecture is very similar to the architecture described in the process described below. The difference is that the components have been replaced with the components below.
However, please pay attention to the following:
• More plenty of coupling compared to components is more important for services; components allow for more closely coupled. This means that according to the requirements of the particle size, you can properly relax the criteria for the use of the processing services discussed above. For finer granularities, the decoupling will weaken advantage. • Processing components can share atomic transaction processing, thereby greatly simplifying the processing design among business services. • Components can be called directly; and unclear messaging is required. Thereby simplifying the processing of abnormal conditions.
figure 1.
Back to top
Analysis
This part discusses business services. Business services can be created as multi-layer systems. A typical business service consists of the following four layers of combinations:
• Services interface. The service interface discloses the functionality that will be seen by the outside world. The addition of the interface is not only easy to openly clear service interfaces, providing convenience for the fulfillment agreement, but also easier to hide the service as an interior interface. • The business processing layer. The business processing layer is responsible for controlling business processing; it defines business processing according to the steps, in addition to the request of the assembly business logic layer, it does not perform any data operations. • Business entity layer. The business entity layer is responsible for performing tasks that need to be completed; it is responsible for implementing the processes of processing. This layer is usually used to design the business entity. Business entity implements business rules, do not store business data, but can maintain references to data entities of stored data. • Data representation layer. Data represents a layer to keep data in the form of a business logic layer. This layer only has universal logic regarding data operation, and does not contain specific knowledge about the business domain. The data representation layer uses a data accessor to store data. It typically uses stored procedures to perform the following: Transfer data between databases and these accessors, and reflecting the difference between the database layout and the data accessor; there is no need to change the code freely transform the design, and no need Change the table freely change the internal data representation.
This optional view is shown in Figure 2.
Figure 2. Layers in business services
Divide the business rules and internal data to separate the ability to make full use of the database usage data, and simultaneous isolation rules without copying logic. For example, when you need to use a list of custom lists in a customer name, the database will provide an efficient way to get the list. The processed process is as follows: first, in turn, through the interface and processing layer, then directly through the business logic layer, and finally enter the data representation layer. This layer will express the request for the database with the formula and generate internal data representation. Now there is no need to make further operations to return the response directly to the requestor.
The internal representation of the data does not have to remain the same as the layout of the database; the stored procedure is used to reflect the difference between the two. And internal representation does not have to be consistent with the format disclosed to the outside world. Other information can be calculated and these information is added to the external structure; some private information can also be filtered. Sometimes it may be possible to disclose a variety of formats to meet the needs of different roles in your organization or meet the access restrictions on these roles.
Figure 3 explains how the service is coupled in a loose manner to couple closely coupled.
Figure 3. System coupled to a relaxed coupling in a loose manner
The service structure is completely used to couple the tight coupling system in loose mode. Although its design goals are not comparable in tight coupling services, excellent design results are usually closely coupled in the service.
Back to top
User interface processing
User Interface Processing provides similar functions to business processing, but they use user interface services instead of business services.
The user interface (UI) of the system consists of a service or component that performs some tasks (such as requesting information from the user or transferring information to the user). These services may be implemented in Microsoft Windows Forms or ASP.NET controls, which are ideal for future reuse. You can use one process to control the interaction between user interface elements to separate operation management from the core business function of the user interface element. Figure 4 explains the implementation of this process.
Figure 4. Explain the implementation of this process
Using processing to control the user interface service to help you isolate the specific user interface of a particular device with more common dialogs and back-end interacts.
Back to top
Conceptual application structure
Figure 5 explains the principle of communicating using user interface services through user interface processing, and then communicating with the service processing service of the service service. The processing between the above communication is responsible for interaction; the agreement between these layers is most important because this may be used by multiple user interface channels.
Figure 5. Concept application structure
Figure 5 consists of two aliquots of two communication with each other: the user interface part of the application and the business part of the application. The infrastructure portion of the structure is separated from the function. Figure 6 explained this view.
Figure 6. Two equal parts of the conceptual application structure
In-depth discussion, you will find business processes that communicate with other business processing in many cases. This is explained in Figure 7.
Figure 7. Business processing in the conceptual application structure
Back to top
Application summary
The application consists of processing services and business services and UI services. Handle the interaction of service control business services and UI services. Business services are usually composed of four layers: service interface, business processing layer, business entity layer, and data representation layer.
This mode is valid for traditional applications and businesses to enterprise solutions. The former has user interfaces that communicate with the business service, which can communicate with each other.
Go to the original English page
