CN111722920A - Load control method - Google Patents

Load control method Download PDF

Info

Publication number
CN111722920A
CN111722920A CN201910220082.3A CN201910220082A CN111722920A CN 111722920 A CN111722920 A CN 111722920A CN 201910220082 A CN201910220082 A CN 201910220082A CN 111722920 A CN111722920 A CN 111722920A
Authority
CN
China
Prior art keywords
service
partition
container
resource
load control
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.)
Pending
Application number
CN201910220082.3A
Other languages
Chinese (zh)
Inventor
李兵
潘军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Digiwin Software Co Ltd
Original Assignee
Digiwin Software Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Digiwin Software Co Ltd filed Critical Digiwin Software Co Ltd
Priority to CN201910220082.3A priority Critical patent/CN111722920A/en
Publication of CN111722920A publication Critical patent/CN111722920A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083Techniques 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)
  • 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 directory to analyze the resource mark; searching in the service container according to the resource identifier to judge whether a corresponding service exists; and when the corresponding service is not searched, searching the corresponding service in the service partition container to read the service partition of the corresponding service and connect the service partition to the corresponding server of the service partition, so that the service request of the client program and the caused server load can be dispersed.

Description

Load control method
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 technique is widely used. The technology can horizontally split the original functions according to actual requirements, and distribute the workload or the task to different programs, devices or nodes.
For example, the load balancing device is connected to a plurality of servers, and dynamically allocates tasks according to the resource usage status of the servers. On the other hand, load balancing is implemented in a software manner, such as Nginx, which requires all servers to be stateless with a default polling and minimal connection manner. However, the load balancing device is expensive, and is not preferred for enterprises with relatively low traffic. In addition, relying on Nginx to achieve load balancing, enterprise software (e.g., ERP) must be stateless at the beginning of design, otherwise subsequent modification and maintenance costs are increased, and the deployed contents of each node are required to be completely consistent. Accordingly, how to efficiently and cost-effectively implement load control is an urgent problem to be solved.
Disclosure of Invention
This summary is provided to provide a simplified summary of the disclosure in order to provide a basic understanding to the reader. This summary is not an extensive overview of the disclosure and is intended to neither identify key/critical elements of the embodiments nor delineate the scope of the embodiments.
According to an 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 directory to analyze the resource mark; searching in the service container according to the resource identifier to judge whether a corresponding service exists; and when the corresponding service is not searched, searching the corresponding service in the service partition container to read the service partition of the corresponding service and connect the service partition to the corresponding server of the service partition so as to disperse the service request of the client program and the caused server load.
In one embodiment, the load control method further includes: 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 includes: reading a function package of a service domain directory, 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 analyzing the at least one function point to write the unique identification into a resource identifier of a service container and write the service partition identifier into an execution service partition of the service container.
In one embodiment, the load control method further includes: reading a transmission parameter of an execution program; and searching in the service container according to the transfer parameter to judge whether relevant data meeting the transfer parameter exists in the service container.
In an embodiment, the step of determining whether the service container has the service partition according with the delivery parameter further comprises: when the service container has the execution service partition meeting the transfer parameter, a service request is distributed to a service partition service container, wherein the service partition service container comprises the data of the at least one function point.
In one embodiment, the step of assigning the service request to the service container of the service partition further comprises: and connecting the service request with the corresponding resource of the resource connection information according to the resource connection information of the service partition service container.
In an embodiment, the step of determining whether the service container has the service partition according with the delivery parameter further comprises: when the service container does not have the execution service partition which meets the transmission parameter, a general service container is executed to search and return a service resource, wherein the general service container comprises 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 one embodiment, the step of retrieving the service container according to the delivery parameter to determine whether the relevant data meeting the delivery parameter exists in the service container further comprises: and searching in the service container according to the business field to judge whether the service container has a resource mark which accords with the business field.
In one embodiment, the step of retrieving the service container according to the delivery parameter to determine whether the relevant data meeting the delivery parameter exists in the service container further comprises: and when the resource mark which accords with the business field exists in the service container, reading the execution business partition corresponding to the resource mark so as to connect to a server corresponding to the execution business partition.
Drawings
The following detailed description, when read in conjunction with the appended drawings, will facilitate a better understanding of aspects of the disclosure. It should be noted that the features in the drawings are not necessarily drawn to scale as may be necessary to illustrate practice. In fact, the dimensions of the various features may be arbitrarily increased or reduced for clarity of discussion.
FIG. 1 illustrates a service process for accounting data in accordance with some embodiments of the present disclosure;
FIG. 2 is a schematic diagram illustrating a client program loading a domain of business directory and a service container in accordance with some embodiments of the present disclosure;
FIG. 3 is a schematic diagram illustrating establishing a resource access link in some embodiments of the present disclosure;
FIG. 4 is a schematic diagram illustrating establishment of a resource access link according to another embodiment of the present disclosure;
FIG. 5 is a flow chart illustrating a load control method according to some embodiments of the present disclosure.
Detailed Description
The following disclosure provides many different embodiments, or examples, for implementing different features of the invention. Specific examples of components 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 that follows 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 second features may not be in direct contact. Additionally, the present disclosure 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) as 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 service process diagram of accounting data according to some embodiments of the present disclosure is shown. A plurality of accounting data may coexist in a target server (not shown), and fig. 1 illustrates the content of one accounting data 100. As shown in fig. 1, the accounting data 100 includes a service partition 110 including connection information 111 and a service partition identification 113. The connection information 111 may be a Uniform resource identifier (Uri) recorded about the service partition and related information about the connection operation. Service partition identifier 113 may be used to identify a service resource classification, for example, if it is a service provider, identifier 113 is an intelligent business event processing (SBEP), report server (ReportServer). In some embodiments, the target server is configured with an accounting data management tool and/or a text editor, and an administrator may directly modify the corresponding accounting data through the accounting data management tool and/or the text editor, for example, add a service partition (BusinessPartition) to the accounting data of the target server to be load balanced or traffic level split. Note that the term "accounting data" in the present disclosure is used interchangeably with "accounting cover" and refers to data related to accounting, finance, and the like.
In one embodiment, the service partition identifier 113 includes an identifier and a communication method. The service partition identification is configured to identify different service resource classifications, such as SBEP, Report Server, and the like. The communication method records the communication technology that a client (e.g. a service consumer or user) can use to connect to a server, such as information of internet address (IP address), port, security identifier, service entry, etc.
For the client program, the administrator can define the client program under the service domain directory (e.g. MONITOR _ EVENT) through the design tool or the editing tool. It should be noted that the domain directory described herein 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 Business Partition Function Point) so that the client program can use the relevant service. The service partition function point (or simply, function point) contains a unique identifier, a service partition identifier of the server program, and a name of the server program (e.g., a name of an Application Program Interface (API)). It is worth mentioning that one or more Function points are included in a Function Package (Function Package), each Function point defining at least one Function or service. Therefore, the aforementioned unique identification of each function point is not repeatable in the same function package.
In one embodiment, after the target server is started, the business 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 entry, etc. The target server stores the read data in the account data model to complete the initialization procedure of the target server.
In one embodiment, one or more client devices are communicatively coupled to the target server. After the client device is started, a login program is executed. During the login, 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 create 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 table one below. 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
Figure BDA0002003303590000051
Referring to FIG. 2, a schematic diagram of a client program loading a domain 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 domain directory 210, at least one function package (not shown) of the domain directory 210 is read, and one or more function points 211 of the function package are read. The function point comprises a unique mark and a service partition mark. An interpreter (not shown) of the client program parses the contents of each function point 211. After parsing out the contents of the function point, the related information of the function point 211 is written into the service container 220.
The service container 220 contains a Resource identifier 221(Resource Key) and an execution service partition 223 (BusinessPartition). The interpreter reads the function point 211 and parses the contents of the function point 211. For example, when the unique identifier of the function point 211 is "IPublishService", the interpreter writes "IPublishService" into the resource identifier 221. In one embodiment, "IPublishService" represents a function that the function point 211 is to provide for publishing update service interfaces. When the service partition of function point 211 is identified as "SBEP," the interpreter writes "SBEP" to executive service partition 223.
In one embodiment, when the resource identifier 221 in the service container records data related to the function point of the service partition, the service container belongs to the service container of the service partition. In other embodiments, when the resource identifier 221 in the service container does not record data related to the function point of the service partition, the service container belongs to a general service container. The service container of the service partition 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 is shown in some embodiments of the present disclosure. After the service container 220 of fig. 2 is built, multiple service containers may be constructed as resource access links. As shown in fig. 3, the client program 390 executes a program for calling a service to acquire a service resource. For example, the client 390 executes a unified executive GetService ("MONITOR _ EVENT", typeof (ipipalishservice)), where a first delivery parameter of the executive GetService () is a service domain and a second delivery parameter is a service type.
In one embodiment, the service container may or may not have an execution service partition that conforms to the delivery parameters. As shown in fig. 3, the client program 390 first obtains the delivery parameters of the executing program, and performs dictionary retrieval comparison in the general service container 310 according to the delivery parameters. If a delivery parameter corresponding to a business domain is retrieved, the client program 390 assigns the corresponding service request to a specified service container, i.e., the business partition service container 320 of FIG. 3. Then, the service partition and the resource connection information (as shown in the above table one) of the service partition service container 320 are used to indicate the operation resource or the service request to the corresponding resource connection. In one embodiment, the service container 320 of the service partition allocates the computational resources to the generic service container 330 or the generic service container 340. In another embodiment, if the delivery parameters corresponding to the business domain are not retrieved from 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 the dependencies and/or calling order between service containers, the service request program of the client program may be distributed in one or more service containers. For example, a publishing service (e.g., "IPublishservice") is delivered to the generic service container 440, and a logging service (ILogService) is invoked after the publishing service is completed, the service being in the generic service container 460.
Referring to fig. 5, a flow chart of a load control method according to some embodiments of the disclosure is shown. 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 reads the domain directory 210 and constructs the service container 220 to parse the resource identifier. In step S530, the client searches the general service container 310 according to the resource identifier to find whether there is a corresponding service.
If the service has no service partition id, step S540 is executed to search for the corresponding service in the general service container 310, and the client program performs a general service container search in a software system (e.g., an enterprise resource planning system (ERP)) and returns the service resource.
If the service has the service partition identifier, step S550 is executed to find a server to be connected to according to the service partition and the resource connection information in the table i. Then, step S560 is executed, in which 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 service partition is SBEP, the client program connects to the SBEP server.
In summary, the load control method disclosed in the present disclosure provides a simple configuration means, and the load in the distribution network can be balanced without purchasing expensive hardware devices (e.g., F5 devices). Furthermore, the present load control method does not require modification of existing function codes and is easy for developers to learn. The technique of the function package and the function point can be implemented as long as the developer understands it. In addition, the load control method provides design of arbitrary granularity (granularity), 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. Those skilled in the art should appreciate 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 introduced herein. Those skilled in the art should also realize that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that they may make various changes, substitutions, and alterations herein without departing from the spirit and scope of the present disclosure.

Claims (10)

1. A method for load control, comprising:
sending a service request through a client program;
reading a service domain directory to analyze a resource mark;
searching in a service container according to the resource identifier to determine whether there is a corresponding service; and
when the corresponding service is not searched, the corresponding service is searched in a service partition container to read a service partition of the corresponding service and a corresponding server connected to the service partition so as to disperse the service request of the client program.
2. The load control method according to claim 1, further comprising:
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.
3. The load control method according to claim 2, further comprising:
reading a function package of a service domain directory, 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
and analyzing the at least one function point to write the unique identification into a resource identifier of a service container and write the service partition identifier into an execution service partition of the service container.
4. The load control method according to claim 3, further comprising:
reading a transmission parameter of an execution program; and
searching in the service container according to the transfer parameter to determine whether there is a relevant data in the service container according with the transfer parameter.
5. The load control method according to claim 4, wherein the step of determining whether the service container has the executive service partition meeting the delivery parameter further comprises:
when the service container has the execution service partition meeting the transfer parameter, a service request is distributed to a service partition service container, wherein the service partition service container comprises the data of the at least one function point.
6. The load control method of claim 5, wherein the step of assigning the service request to the service container of the service partition further comprises:
and connecting the service request with the corresponding resource of the resource connection information according to the resource connection information of the service partition service container.
7. The load control method according to claim 4, wherein the step of determining whether the service container has the executive service partition meeting the delivery parameter further comprises:
when the service container does not have the execution service partition which meets the transmission parameter, a general service container is executed to search and return a service resource, wherein the general service container comprises the data of the at least one function point.
8. The method of claim 2, further comprising establishing a resource access link according to a plurality of the service containers.
9. The load control method according to claim 4, wherein the delivery parameters include a service domain and a service type, and wherein the step of retrieving from the service container according to the delivery parameters to determine whether the associated data corresponding to the delivery parameters exists in the service container further comprises:
and searching in the service container according to the business field to judge whether the service container has a resource mark which accords with the business field.
10. The load control method according to claim 9, wherein the step of retrieving the service container according to the transfer parameter to determine whether the associated data corresponding to the transfer parameter exists in the service container further comprises:
and when the resource mark which accords with the business field exists in the service container, reading the execution business partition corresponding to the resource mark so as to connect to a server corresponding to the execution business partition.
CN201910220082.3A 2019-03-22 2019-03-22 Load control method Pending CN111722920A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910220082.3A CN111722920A (en) 2019-03-22 2019-03-22 Load control method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910220082.3A CN111722920A (en) 2019-03-22 2019-03-22 Load control method

Publications (1)

Publication Number Publication Date
CN111722920A true CN111722920A (en) 2020-09-29

Family

ID=72563570

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910220082.3A Pending CN111722920A (en) 2019-03-22 2019-03-22 Load control method

Country Status (1)

Country Link
CN (1) CN111722920A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110040892A1 (en) * 2009-08-11 2011-02-17 Fujitsu Limited Load balancing apparatus and load balancing method
CN103259739A (en) * 2012-02-15 2013-08-21 株式会社日立制作所 Load balancing device and load balancing method
CN104079630A (en) * 2014-06-09 2014-10-01 中国建设银行股份有限公司 Business server side load balancing method, client side, server side and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110040892A1 (en) * 2009-08-11 2011-02-17 Fujitsu Limited Load balancing apparatus and load balancing method
CN103259739A (en) * 2012-02-15 2013-08-21 株式会社日立制作所 Load balancing device and load balancing method
CN104079630A (en) * 2014-06-09 2014-10-01 中国建设银行股份有限公司 Business server side load balancing method, client side, server side and system

Similar Documents

Publication Publication Date Title
CN110535831B (en) Kubernetes and network domain-based cluster security management method and device and storage medium
US11711420B2 (en) Automated management of resource attributes across network-based services
US9420034B2 (en) Providing services to multiple tenants of an application
US8903996B2 (en) Operating cloud computing services and cloud computing information system
US7761527B2 (en) Method and apparatus for discovering network based distributed applications
US10623262B2 (en) Methods and systems to adjust a monitoring tool and auxiliary servers of a distributed computing system
US20030167401A1 (en) Definition of low-level security rules in terms of high-level security concepts
US20190163550A1 (en) Automated methods and systems to classify and troubleshoot problems in information technology systems and services
TW201220189A (en) Method and apparatus for service deployment from a service registry
US10552293B2 (en) Logging as a service
Baresi et al. Microservices: The evolution and extinction of web services?
US10019293B2 (en) Enhanced command selection in a networked computing environment
AU2014400621B2 (en) System and method for providing contextual analytics data
US10397051B1 (en) Configuration and testing of network-based service platform resources using a service platform specific language
US7937711B2 (en) Method and apparatus for providing a consolidated namespace to client applications in multi-tenant common information model (CIM) environments
US10182104B1 (en) Automatic propagation of resource attributes in a provider network according to propagation criteria
CN111984505A (en) Operation and maintenance data acquisition engine and acquisition method
CN107222575A (en) Realize the method that OPC communicates between industrial control equipment
US7543300B2 (en) Interface for application components
CN111722920A (en) Load control method
TWI702540B (en) Load control method
CN111176782B (en) Online experiment method and device
CN113067878A (en) Information acquisition method, information acquisition device, information acquisition apparatus, information acquisition medium, and program product
CN111651330A (en) Data acquisition method and device, electronic equipment and computer readable storage medium
US20040268362A1 (en) Method, apparatus and program storage device for providing a two-step communication scheme

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