CN111722920B - Load control method - Google Patents
Load control method Download PDFInfo
- Publication number
- CN111722920B CN111722920B CN201910220082.3A CN201910220082A CN111722920B CN 111722920 B CN111722920 B CN 111722920B CN 201910220082 A CN201910220082 A CN 201910220082A CN 111722920 B CN111722920 B CN 111722920B
- Authority
- CN
- China
- Prior art keywords
- service
- partition
- container
- business
- service container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present disclosure provides a load control method. The load control method comprises the following steps: issuing a service request via a client program; reading the service domain catalogue to analyze the resource mark; searching in the service container according to the resource mark to judge whether the corresponding service exists or not; and searching the corresponding service in the service partition container when the corresponding service is not searched, so as to read the service partition of the corresponding service and connect to the corresponding server of the service partition, thereby distributing the service request of the client program and the caused server load.
Description
Technical Field
The present disclosure relates to a control method, and more particularly, to a control method of a load.
Background
In a network software system, a load control technology is a widely used technology. The technology can split the original functions horizontally according to actual demands, and distributes workload or tasks to different programs, devices or nodes.
For example, the load balancing technique is generally implemented in hardware, for example, a load balancing device is connected to a plurality of servers, and tasks are dynamically allocated according to resource usage conditions of the servers. On the other hand, load balancing is implemented in a software manner, such as nmginx, which already defaults to polling and minimal connectivity, requiring all servers to be stateless. However, load balancing devices are expensive and are not preferred for businesses with relatively low traffic. Moreover, depending on the manner in which the nmginx achieves load balancing, at the outset of the design, enterprise software (e.g., ERP) must go stateless, otherwise subsequent modification and maintenance costs will be increased, and the content of each node deployment is required to be completely consistent. Accordingly, how to efficiently and cost effectively implement load control is a problem to be solved.
Disclosure of Invention
This summary is intended to provide a simplified summary of the disclosure so that the reader is a basic understanding of the disclosure. This summary is not an extensive overview of the disclosure and is intended to neither identify key/critical elements of the embodiments of the invention nor delineate the scope of the invention.
According to one embodiment of the present disclosure, a load control method is disclosed. The load control method comprises the following steps: issuing a service request via a client program; reading the service domain catalogue to analyze the resource mark; searching in the service container according to the resource mark to judge whether the corresponding service exists or not; and searching the corresponding service in the service partition container when the corresponding service is not searched, so as to read the service partition of the corresponding service and connect to the corresponding server of the service partition, and disperse the service request of the client program and the caused server load.
In one embodiment, the load control method further comprises: selecting one of a plurality of accounting data; and analyzing the content of the account data to establish a service request program, wherein the service request program comprises a service partition and resource connection information.
In one embodiment, the load control method further comprises: reading a function package of a service domain catalog, wherein the function package comprises at least one function point; reading the at least one function point of the function package, wherein each function point comprises a unique identification; and resolving the at least one functional point to write the unique identification to a resource identifier of a service container and to write the service partition identifier to an execution service partition of a service container.
In one embodiment, the load control method further comprises: reading a transfer parameter of an execution program; and searching in the service container according to the transfer parameter to judge whether the service container has a related data which accords with the transfer parameter.
In one embodiment, the step of determining whether the execution service partition conforming to the delivery parameter exists in the service container further comprises: and when the execution service partition conforming to the transmission parameter exists in the service container, distributing a service request to a service partition service container, wherein the service partition service container contains the data of the at least one function point.
In one embodiment, the step of assigning the service request to the business partition service container further comprises: and according to the resource connection information of the service partition service container, connecting the service request with the corresponding resource of the resource connection information.
In one embodiment, the step of determining whether the execution service partition conforming to the delivery parameter exists in the service container further comprises: when the execution service partition conforming to the transfer parameter does not exist in the service container, a general service container is executed to search and return a service resource, wherein the general service container contains the data of the at least one function point.
In one embodiment, the load control method further comprises establishing a resource access link according to a plurality of the service containers.
In an embodiment, the delivery parameter includes a service domain and a service type, wherein the step of searching in the service container according to the delivery parameter to determine whether the service container has the relevant data corresponding to the delivery parameter further includes: searching in the service container according to the service field to judge whether the service container has a resource mark conforming to the service field.
In one embodiment, the step of searching in the service container according to the transfer parameter to determine whether the service container has the relevant data corresponding to the transfer parameter further comprises: and when the resource mark conforming to the service field exists in the service container, reading the execution service partition corresponding to the resource mark so as to be connected to a server corresponding to the execution service partition.
Drawings
The following detailed description, when read in conjunction with the accompanying drawings, will facilitate a better understanding of the aspects of the present disclosure. It should be noted that the features in the drawings are not necessarily drawn to scale according to the requirements of the actual implementation in the description. In fact, the dimensions of the various features may be arbitrarily increased or decreased for clarity of discussion.
FIG. 1 is a schematic diagram of a service process for accounting data according to some embodiments of the present disclosure;
FIG. 2 is a schematic diagram of a client program loading business domain directory and a service container according to some embodiments of the present disclosure;
FIG. 3 is a schematic diagram illustrating the establishment of a resource access link in some embodiments of the present disclosure;
FIG. 4 is a schematic diagram of establishing a resource access link in other embodiments of the present disclosure;
Fig. 5 is a flow chart illustrating a load control method according to some embodiments of the disclosure.
Detailed Description
The following disclosure provides many different embodiments, or examples, for implementing different features of the invention. Specific examples of elements and arrangements are described below to simplify the present disclosure. Of course, these examples are merely illustrative and are not intended to be limiting. For example, forming a first feature over or on a second feature in the description below may include embodiments in which the first and second features are formed in direct contact, and may also include embodiments in which additional features may be formed between the first and second features such that the first and features may not be in direct contact. In addition, the present invention may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.
Further, spatially relative terms, such as "under," "below," "lower," "above," "higher," and the like, may be used herein for ease of description to describe one element or feature's relationship to another element (or elements) or feature (or features) illustrated in the figures. Spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. The apparatus may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.
Referring to fig. 1, a schematic diagram of a service procedure of account data according to some embodiments of the present disclosure is shown. Multiple accounting data may exist at the same time on a destination server (not shown), and fig. 1 illustrates the contents of one of the accounting data 100. As shown in fig. 1, accounting data 100 includes a traffic partition 110 including connection information 111 and a traffic partition identification 113. The connection information 111 may be a universal resource identifier (Uri, uniform resource identifier) recorded on the service partition and related information on the connection operation. The service partition identifier 113 may be used to identify a service resource class, such as, for example, if a service provider, an intelligent business event process (SBEP), report Server (Report Server). In some embodiments, the target server is configured with an accounting data management tool and/or text editor through which an administrator may directly modify corresponding accounting data, such as adding a business partition (Business Partition) to the accounting data of the target server to be load balanced or business level split. It should be noted that the term "account data" in the present disclosure may be used interchangeably with "account cover" to refer to data related to accounting or finance.
In one embodiment, the service partition identifier 113 includes an identifier and a communication mode. The traffic partition identification is configured to identify different traffic resource classifications, such as SBEP, report Server, etc. The communication means records information such as internet address (IP address), port, security identifier, service portal, etc. that the client program (e.g., service consumer or user) can use to connect to the server.
For client programs, the manager may define the client program under a domain of business directory (e.g., monitor_event) through a design tool or an editing tool. It should be noted that the service domain directory may be a directory of folders in a computer operating system, or a hierarchical directory of virtual folders. In one embodiment, the target server provides the client program to connect through an interface (e.g., a service partition function point Business Partition Function Point)) such that the client program uses the associated service. The service partition function point (or simply function point) contains a unique identification, a service partition identification of the server program, and a name of the server program (e.g., a name of an Application Program Interface (API)). It should be noted that one or more Function points are included in a Function Package (Function Package), and each Function point defines at least one Function or service. Thus, the unique identification of each of the aforementioned function points is not repeatable in the same function package.
In one embodiment, after the target server is started, the service partition 110 of each accounting data 100 shown in fig. 1 is loaded to read the configuration of each accounting data 100, such as Internet Protocol (IP) address, port, security label, service portal, etc. And the target server stores the read data in an account data model to finish the initialization program of the target server.
In one embodiment, one or more client devices are communicatively coupled to a target server. After the client device is started, the login procedure is executed. During the login process, one of the accounting data 100 in the accounting data model is selected on the target server.
The client device then parses the accounting data 100 to establish a service request procedure. For example, the client program reads the service partition 110 in the accounting data 100 and establishes the resource connection information corresponding to the service partition 110 as shown in the following table one. And the client program reads the corresponding resource connection information according to the service partition so as to use the service request program indicated by the resource connection information.
Table one: service request program
Referring to FIG. 2, a schematic diagram of a client program loading business segment directory 210 and a service container 220 according to some embodiments of the present disclosure is shown. As shown in fig. 2, when the client program reads the service domain directory 210, it reads at least one function packet (not shown) of the service domain directory 210, and reads one or more function points 211 of the function packet. The function point contains a unique identifier and a service partition identifier. An interpreter (not shown) of the client program parses the contents of each function point 211. After analyzing the content of the function point, the relevant information of the function point 211 is written into the service container 220.
Service container 220 contains Resource Key 221 and execution service partition 223 (Business Partition). The interpreter reads the function point 211 and parses the contents of the function point 211. For example, when the unique identification of the function point 211 is "IPublishService", the interpreter writes "IPublishService" to the resource identifier 221. In one embodiment, "IPublishService" represents the function point 211 that is used to provide the functionality of the post update service interface. When the service partition of functional point 211 is identified as "SBEP," then the interpreter writes "SBEP" to the executive service partition 223.
In one embodiment, when the resource identifier 221 in the service container records data about the service partition's function point, the service container belongs to the service partition service container. In other embodiments, a service container belongs to a generic service container when the resource identifier 221 in the service container does not record data about the functional point of the service partition. Wherein, the business partition service container and the general service container both contain data of at least one function point.
Referring to fig. 3, a schematic diagram of establishing a resource access link 300 in some embodiments of the present disclosure is shown. After the service container 220 of fig. 2 is established, multiple service containers may be constructed as resource access links. As shown in FIG. 3, client program 390 executes a program that invokes a service to retrieve a service resource. For example, the client program 390 executes a unified executive GetService ("monitor_event", typeof (IPublishService)), wherein the first delivery parameter of the executive GetService () is the traffic domain and the second delivery parameter is the service type.
In one embodiment, the service container may or may not have an execution traffic partition that meets the delivery parameters. As shown in fig. 3, the client program 390 first acquires transfer parameters of the execution program and performs dictionary search comparison in the general service container 310 according to the transfer parameters. If delivery parameters corresponding to the business segment are retrieved, client program 390 assigns the corresponding service request to the specified service container, i.e., business partition service container 320 of FIG. 3. Then, the operation resource or service request is indicated to the corresponding resource connection by the service partition and resource connection information (as in the first embodiment) of the service partition service container 320. In one embodiment, the business partition service container 320 allocates computing resources to either the generic service container 330 or the generic service container 340. In another embodiment, if the delivery parameters corresponding to the service domain are not retrieved in the generic service container 310, a generic service container search is performed and service data is returned according to the search result.
Referring to FIG. 4, a schematic diagram of establishing a resource access link 400 in other embodiments of the present disclosure is shown. The difference between the resource access link 400 of fig. 4 and the resource access link 300 of fig. 3 is that the resource access link 400 of fig. 4 includes more than one traffic partition service container (e.g., traffic partition service container 420 and traffic partition service container 450). Because of dependencies and/or call order among the service containers, the service request program of the client program may be distributed among one or more service containers. For example, a publication service (e.g., "IPublishService") is transferred to the generic service container 440, and a log service (ILogService) is invoked after the publication service is completed, which is in the generic service container 460.
Fig. 5 is a flow chart illustrating a load control method according to some embodiments of the disclosure. The following description refers to fig. 2, 3 and 5. In step S510, the client device requests a service, for example, issues a service request of "IPublishService". In step S520, the client program reads the service domain directory 210, and constructs the service container 220 to parse the resource identifier. In step S530, the client program searches the generic service container 310 according to the resource identifier to find whether there is a corresponding service.
If the service has no service partition identifier, step S540 is performed to find the corresponding service in the generic service container 310, and the client program performs the generic service container search in a software system (e.g., enterprise resource planning system (ERP)) and returns the service resource.
If the service has the service partition identifier, step S550 is executed to find the server to be connected to according to the service partition and the resource connection information in the table one. Next, step S560 is executed, where the client service connects to the server corresponding to the service partition and the resource connection information, and returns the service resource. For example, when the traffic partition is SBEP, the client program connects to SBEP server.
In summary, the load control method disclosed in the present disclosure provides a simple configuration means, and does not require purchasing expensive hardware devices (e.g. F5 devices) to balance the load in the distribution network. In addition, the present load control method does not require modification of existing function codes, and is easy for a developer to learn. The techniques of the function packages and the function points can be implemented as long as the developer understands them. In addition, the load control method provides arbitrary granularity (granularity) design, supports service level splitting, and can provide high-ductility load balancing operation.
The foregoing outlines features of several embodiments so that those skilled in the art may better understand the aspects of the present disclosure. It should be appreciated by those skilled in the art that the present invention may be readily utilized as a basis for designing or modifying other processes and structures for carrying out the same purposes and/or achieving the same advantages of the embodiments presented herein. It should also be realized by those skilled in the art that such equivalent constructions do not depart from the spirit and scope of the invention, and that they may make various changes, substitutions and alterations herein without departing from the spirit and scope of the invention.
Claims (10)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910220082.3A CN111722920B (en) | 2019-03-22 | 2019-03-22 | Load control method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910220082.3A CN111722920B (en) | 2019-03-22 | 2019-03-22 | Load control method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111722920A CN111722920A (en) | 2020-09-29 |
| CN111722920B true CN111722920B (en) | 2024-06-21 |
Family
ID=72563570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910220082.3A Active CN111722920B (en) | 2019-03-22 | 2019-03-22 | Load control method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111722920B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104079630A (en) * | 2014-06-09 | 2014-10-01 | 中国建设银行股份有限公司 | Business server side load balancing method, client side, server side and system |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101227415A (en) * | 2008-02-04 | 2008-07-23 | 华为技术有限公司 | Multi-service resource allocation method, system, gateway device and authentication server |
| JP5338555B2 (en) * | 2009-08-11 | 2013-11-13 | 富士通株式会社 | Load distribution apparatus, load distribution method, and load distribution program |
| CN103259739A (en) * | 2012-02-15 | 2013-08-21 | 株式会社日立制作所 | Load balancing device and load balancing method |
| CN104461736B (en) * | 2014-12-08 | 2018-11-30 | 畅捷通信息技术股份有限公司 | Resource allocation and searching method, resource allocation and search system and Cloud Server |
| US10404791B2 (en) * | 2015-12-04 | 2019-09-03 | Microsoft Technology Licensing, Llc | State-aware load balancing of application servers |
| CN108737467B (en) * | 2017-04-19 | 2021-03-26 | 腾讯科技（深圳）有限公司 | Server log viewing method, device and system |
-
2019
- 2019-03-22 CN CN201910220082.3A patent/CN111722920B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104079630A (en) * | 2014-06-09 | 2014-10-01 | 中国建设银行股份有限公司 | Business server side load balancing method, client side, server side and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111722920A (en) | 2020-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11711420B2 (en) | Automated management of resource attributes across network-based services | |
| US10735345B2 (en) | Orchestrating computing resources between different computing environments | |
| CN107431651B (en) | Life cycle management method and equipment for network service | |
| US7730183B2 (en) | System and method for generating virtual networks | |
| CN102446121B (en) | Allocating virtual machines according to user-specific virtual machine metrics | |
| US10891569B1 (en) | Dynamic task discovery for workflow tasks | |
| US20090199172A1 (en) | Apparatus and method for importing language extension resources to support application execution | |
| US20190163550A1 (en) | Automated methods and systems to classify and troubleshoot problems in information technology systems and services | |
| CN112256439B (en) | Service directory dynamic updating system and method based on cloud computing resource pool | |
| US10397051B1 (en) | Configuration and testing of network-based service platform resources using a service platform specific language | |
| CN106453576B (en) | A kind of exchange method, system and control centre based on mixing cloud platform | |
| TW201220189A (en) | Method and apparatus for service deployment from a service registry | |
| CN102576354A (en) | Extensible framework to support different deployment architectures | |
| CN112764873B (en) | The method of instantiating NS and NFVO | |
| US20100050179A1 (en) | Layered capacity driven provisioning in distributed environments | |
| US20050223101A1 (en) | Computer-implemented method, system and program product for resolving prerequisites for native applications utilizing an open service gateway initiative ( OSGi) framework | |
| US7818752B2 (en) | Interface for application components | |
| US7302477B2 (en) | Administration tool for gathering information about systems and applications including the feature of high availability | |
| CN111885190A (en) | Service request processing method and system | |
| US20050192965A1 (en) | Method and apparatus for discovering network based distributed applications | |
| CN114930788B (en) | Method and system for securely processing integrated message flows in a multi-tenant container | |
| US12299134B1 (en) | Knowledge-based taint policy inference | |
| EP1061445A2 (en) | Web-based enterprise management with transport neutral client interface | |
| CN111722920B (en) | Load control method | |
| US7937711B2 (en) | Method and apparatus for providing a consolidated namespace to client applications in multi-tenant common information model (CIM) environments |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20200929 Assignee: Shanghai Dingjie Shuzhi Software Co.,Ltd. Assignor: DIGIWIN SOFTWARE Co.,Ltd. Contract record no.: X2024310000112 Denomination of invention: Load control method Granted publication date: 20240621 License type: Common License Record date: 20240903 |
|
| EE01 | Entry into force of recordation of patent licensing contract | ||
| CP03 | Change of name, title or address |
Address after: 20th Floor, No. 7, Lane 1377, Jiangchang Road, Jing'an District, Shanghai, 200400 Patentee after: Dingjie Shuzhi Co.,Ltd. Country or region after: China Address before: 200443 22F, building 1, central Greenland, Lane 1377, JIANGCHANG Road, Shanghai Patentee before: DIGIWIN SOFTWARE Co.,Ltd. Country or region before: China |
|
| CP03 | Change of name, title or address |