CN114036031B - Scheduling system and method for resource service application in enterprise digital middleboxes - Google Patents
Scheduling system and method for resource service application in enterprise digital middleboxes Download PDFInfo
- Publication number
- CN114036031B CN114036031B CN202210006017.2A CN202210006017A CN114036031B CN 114036031 B CN114036031 B CN 114036031B CN 202210006017 A CN202210006017 A CN 202210006017A CN 114036031 B CN114036031 B CN 114036031B
- Authority
- CN
- China
- Prior art keywords
- resource service
- service application
- application identifier
- thread group
- resource
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a system and a method for scheduling resource service application in an enterprise digital middlebox, wherein the system comprises: the resource service application identifier configuration library is positioned in the enterprise digital center, the resource service application center and a local monitoring platform corresponding to the resource service application center; the resource service application identifier configuration library is used for storing a resource service application identifier list of resource service application identifiers; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene; and the local monitoring platform acquires a plurality of resource service requests of the resource service application middle station, respectively routes the resource service requests to a thread group which is created according to the resource service application identification list and corresponds to the resource service application identification. Therefore, the north and south isolation of the resource service request flow of different resource service applications is realized.
Description
Technical Field
The application relates to the technical field of computers, in particular to a scheduling system, a scheduling method and a scheduling device for resource service application in an enterprise digital middlebox. The application also relates to a computer storage medium and an electronic device.
Background
With the continuous development of science and technology, computer foundations such as informatization, intellectualization and the like are widely applied to various industry fields and daily life. Driven by industry and technology, digital transformation has become a consensus of enterprises. The Digital transformation (Digital transformation) is established on the basis of Digital transformation (Digitization) and Digital upgrading (Digitization), and can touch the core business of an enterprise and establish transformation with a business operation mode as a target.
With the continuous promotion and deepening of enterprise sharing capacity in a digital service mode, in order to deposit the core capacity of an enterprise to a platform in a digital form along with the continuous development of services, the digital middlings which take the services as the center and construct an operation system with data closed-loop operation by the business middlings and the data middlings become an effective system form and an organization method for the digital transformation of the enterprise, so that the enterprise can more efficiently conduct business exploration and innovation, and the purpose of constructing the core differentiated competitiveness of the enterprise in the form of digital assets is achieved.
Disclosure of Invention
The application provides a scheduling system of resource service application in an enterprise digital middlebox, which aims to solve the problems of inflexible flow isolation request mode and resource waste in the middlebox in the prior art.
The application provides a scheduling system of resource service application in an enterprise digital middle station, which comprises: the system comprises a resource service application identifier configuration library, a resource service application middle station and a local monitoring platform corresponding to the resource service application middle station, wherein the resource service application identifier configuration library is positioned in the enterprise digital middle station;
the resource service application identifier configuration library is used for storing a resource service application identifier list of resource service application identifiers; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
and the local monitoring platform acquires a plurality of resource service requests of the resource service application middle station, respectively routes the resource service requests to a thread group which is created according to the resource service application identification list and corresponds to the resource service application identification.
In some embodiments, the local monitoring platform obtains the resource service application identifier list in the resource service application identifier configuration library, and creates the thread group corresponding to the resource service application identifier according to the resource service application identifier in the resource service application identifier list.
In some embodiments, the local monitoring platform obtains execution status data of the thread group executing the resource service request; and carrying out capacity expansion or capacity reduction on the thread group according to the execution state data.
In some embodiments, the resource service application identification configuration repository further stores execution state data of the thread group executing the resource service request.
In some embodiments, further comprising: the global monitoring platform is used for acquiring execution state data of the resource service request matched with the resource service application identifier in the resource service application identifier configuration library; and determining to perform capacity expansion or capacity reduction on the resource service application middlings according to the execution state data.
In some embodiments, further comprising:
and the display device is used for displaying at least one of load state information of the thread group, resource service request quantity information corresponding to the current resource service application identifier, thread group information corresponding to the current resource service application identifier, thread quantity information of the thread group, request quantity information processed by the thread group, idle state information of the thread group, release information of the thread group and capacity expansion information of a middle station of the resource service application on an interface.
The application also provides a method for scheduling resource service application in the enterprise digital middleboxes, which comprises the following steps:
creating a thread group which is positioned in a resource service application middle station and corresponds to the resource service application identifier according to the acquired resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
acquiring a plurality of resource service requests of a resource service application center;
and respectively routing the resource service requests to the thread groups matched with the resource service application identifications.
In some embodiments, the creating, according to the obtained resource service application identifier, a thread group located in a resource service application middleware and corresponding to the resource service identifier includes:
responding to a starting event of the resource service application middle station, and acquiring a resource service application identifier list for storing the resource service application identifier;
and creating the thread group corresponding to the resource service application identifier according to the resource service application identifier list.
In some embodiments, further comprising:
acquiring execution state data of the thread group for executing the resource service request;
and carrying out capacity expansion or capacity reduction on the thread group according to the execution state data.
In some embodiments, further comprising:
and sending the execution state data to the resource service application identification list.
The application also provides a method for scheduling resource service application in the enterprise digital middleboxes, which comprises the following steps:
acquiring a resource service request execution state of the resource service application identifier in a resource service application identifier list; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
according to the resource service request execution state, carrying out capacity expansion or capacity reduction on the resource service application middlebox; the resource service application middle station comprises a thread group which is established according to the acquired resource service application identifier, is positioned in the resource service application middle station and corresponds to the resource service application identifier.
The application also provides a method for scheduling resource service application in the enterprise digital middleboxes, which comprises the following steps:
the local monitoring platform establishes a thread group which is positioned in a resource service application middle station and corresponds to the resource service application identifier according to the acquired resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
the local monitoring platform acquires a plurality of resource service requests of a resource service application center; the local monitoring platform corresponds to the resource service application middle platform;
the local monitoring platform routes the resource service requests to the thread groups matched with the resource service application identifiers respectively;
responding to the resource service request execution state of the resource service application identifier in the resource service application identifier list sent by the local monitoring platform by the global monitoring platform, and performing capacity expansion or capacity reduction on the resource service application middlebox.
The application also provides a computer storage medium for storing the data generated by the network platform and a program for processing the data generated by the network platform;
when the program is read and executed by a processor, the program executes the scheduling method of the resource service application in the enterprise digital center; or, executing the scheduling method of the resource service application in the enterprise digital center station; alternatively, the scheduling method of the resource service application in the enterprise digital center as described above is performed.
The present application further provides an electronic device, comprising:
a processor;
a memory for storing a program for processing data generated by the network platform, wherein the program, when read and executed by the processor, executes the scheduling method of the resource service application in the enterprise digital center; or, executing the scheduling method of the resource service application in the enterprise digital center station; alternatively, the scheduling method of the resource service application in the enterprise digital center as described above is performed.
Compared with the prior art, the method has the following advantages:
according to the scheduling system of the enterprise digital middlebox resource service application, on one hand, the acquired resource service requests can be routed to the thread groups corresponding to the resource service application identifications created according to the resource service application identification list through the local monitoring platform, so that the resource service requests can be processed in the corresponding thread groups, and the north-south isolation of the resource service request flow of different resource service applications is realized; on the other hand, the capacity expansion or capacity reduction of the resource service application middle station can be realized according to the execution state data of the resource service request matched with the resource service application identifier in the resource service application identifier configuration library acquired by the global monitoring platform, so that the resource waste is avoided, and the precise scheduling and adjustment of the resource service request are realized.
Drawings
Fig. 1 is a schematic structural diagram of an embodiment of a scheduling system for resource service applications in an enterprise digital middlebox provided by the present application.
Fig. 2 is a flowchart of an embodiment from the perspective of a local monitoring platform in a scheduling method for resource service applications in an enterprise digital middlebox according to the present application.
Fig. 3 is a schematic structural diagram of an embodiment of a scheduling apparatus for resource service application in an enterprise digital middlebox from the perspective of a local monitoring platform according to the present application.
Fig. 4 is a flowchart of an embodiment in terms of a global monitoring platform in a scheduling method for resource service applications in an enterprise digital middlebox according to the present application.
Fig. 5 is a schematic structural diagram of an embodiment of a scheduling apparatus for resource service applications in an enterprise digital middlebox from the perspective of a global monitoring platform according to the present application.
Fig. 6 is a flowchart of an embodiment in terms of local and global monitoring platforms in a scheduling method for resource service applications in an enterprise digital middlebox according to the present application.
Fig. 7 is a schematic structural diagram of an embodiment in terms of local and global monitoring platforms in a scheduling apparatus for resource service applications in an enterprise digital middlebox according to the present application.
Fig. 8 is a schematic structural diagram of an embodiment of an electronic device provided in the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The description used in this application and in the appended claims refers to the accompanying drawings in which: the terms "a," "an," "first," and "second," etc., are not intended to be limiting in number or order, but rather are used to distinguish one type of information from another.
By combining the background technologies, the enterprise digital middle station is service-oriented capability combination, sharing and multiplexing, provides an integrated solution, and aims to improve research and development efficiency and reduce innovation cost. The enterprise digital center station can comprise users, combinations, platforms, data, standards and specifications, and is an integral system of the users and the system. Namely: the enterprise digital middle platform is an enterprise level capability multiplexing platform which abstracts the common requirements of enterprises, creates platform and component system capabilities and shares the platform and the component system capabilities to each service unit in the forms of interfaces, components and the like.
The enterprise digital middleboxes provide services for each application in a shared manner, so that the application services become one of the key entities in the enterprise digital middleboxes. Under the background of a sharing mode, the fact that each application service is not affected by each other is one of important factors for normal operation of an enterprise digital middlebox, and the existing traffic isolation for each application service in the enterprise digital middlebox usually adopts a physical isolation mode, that is, different middlebox application instances are deployed for different application services, so that isolation of application service traffic in the south-north direction of the enterprise digital middlebox is realized, however, the physical isolation mode has the following problems:
1. multiple middle platform application examples are deployed in a manual mode, and the method is not flexible;
2. the application example of the middle platform is separately deployed for the application service, and resource allocation cannot be performed according to the actual flow state, so that resource waste is caused.
In view of this, the present application provides a system and a method for scheduling resource service applications in an enterprise digital middlebox, which can solve the problems of inflexible application instances and resource waste in manual deployment of middlebox applications.
Fig. 1 is a schematic structural diagram of an embodiment of a scheduling system for resource service applications in an enterprise digital middlebox according to the present application; the embodiment of the scheduling system comprises: a resource service application identifier configuration library 101, a resource service application center 102 in an enterprise digital center, and a Local monitoring platform (Local Monitor) 103 corresponding to the resource service application center;
the resource service application identifier configuration library 101 is configured to store a resource service application identifier list of resource service application identifiers; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene. The identity of the application service participating in the application scenario may be referred to as a service identity, which is an independent service unit of the platform executing the working capability in the resource service application. Invoking authentication for capability access and routing policy implemented by the extension point. The service identity may be a level of resource service application, and multiple resource service applications may exist for the same user, and different resource service applications have different identity levels or may belong to the same identity level. The identity level of the resource service application may further include a sub-identity level, that is, an identity level of an overall link capable of distinguishing the resource service application. For example: the application 1 is a primary service identity, the application 2 is also a primary service identity, and the application 3 belongs to the application 1 and is a secondary service identity.
In this embodiment, the resource service application may be various application services, for example: living, shopping, medicine, etc. The resource service may be, for example: and the functional services of commodity information inquiry, commodity state management, order inquiry service and the like. The resource service application identification list may also be referred to as a resource service identity configuration list, which stores a list of resource service application identity information. The resource service identity configuration list may also store traffic processing data corresponding to the resource service application identity information, which is transmitted by the local monitoring platform 103, for example: query Per Second (QPS), latency rate, throughput, etc.
The local monitoring platform 103 acquires the resource service request of the station 102 in the resource service application, and routes the resource service request to a thread group corresponding to the resource service application identifier, which is created according to the resource service application identifier list; wherein the thread group executes the resource service requests identified by one or more same resource service applications.
In this embodiment, the resource service application middlebox 102 can be constructed by an enterprise digital middlebox. The local monitoring platform 103 obtains the resource service application identifier list in the resource service application identifier configuration library 101, and creates the thread group (group) corresponding to the resource service application identifier according to the resource service application identifier in the resource service application identifier list, for example, the thread group1 and the thread group 2.
When the resource service application middle station 102 is started, the local monitoring platform 103 reads the resource service application identifier list in the resource service application identifier configuration library 101. And the local monitoring platform 103 creates the thread group according to the read resource service application identification list. The resource service request initiated by the terminal device is transmitted to the resource service application center station 102, and the resource service application center station 102 routes the resource service request to the thread groups according to the resource service application identifiers. For example: the resource service application identifier configuration library 101 stores resource service application identifiers of a resource service application 1, a resource service application 2, a resource service application 3 and a resource service application 4. The resource service request may be a request for one or more of resource service application 1, resource service application 2, and resource service application 3, and the resource service request for each resource service application may be one or more request contents, such as an access request, an order request, a payment request, and the like. When the resource service application middle platform is started, the local monitoring platform reads the identifier in the resource service application identifier configuration library, and then creates a corresponding thread group for the resource service application identifier, namely, the thread group1 corresponds to the resource service request of the resource service application 1, the thread group2 corresponds to the resource service request of the resource service application 2, the thread group 3 corresponds to the resource service request of the resource service application 3, and the thread group 4 corresponds to the resource service request of the resource service application 4. Thread group1, thread group2, thread group 3, and thread group 4 may constitute a thread group set. The resource service requests initiated to the resource service application 1, the resource service application 2, the resource service application 3, the resource service application 4, and the like are transmitted to the local monitoring platform 103, the local monitoring platform 103 routes the resource service request 1 to the thread group1 according to the resource service application identifier, the request 2 is routed to the thread group2, the request 3 is routed to the thread group 3, and the request 4 is routed to the thread group 4, so that the requests 1 and 4 are independent from each other, and traffic isolation is achieved. Of course, according to the state of the actual request traffic, resource service requests identified by different resource service applications may also be routed to the same thread group, thereby reducing resource waste, because, in the case of a small request traffic, the influence between the resource service applications may be ignored, or the generated influence may not relate to the running state between the resource service applications.
In this embodiment, to avoid resource waste, the execution state data of the thread group executing the resource service request may be obtained by the local monitoring platform 103, and the capacity of the thread group is expanded or reduced according to the execution state data. The execution state data may include: request traffic handling data corresponding to resource service application identity information, for example: query Per Second (QPS), latency rate, throughput, etc. When the query rate and/or the delay rate are/is large, it is indicated that the request flow is large or in a saturated state, capacity expansion needs to be performed on the thread group, and otherwise, capacity reduction is performed. When the throughput is larger, the request flow is smaller, and the capacity can be reduced for the thread group, otherwise, the capacity can be expanded.
In this embodiment, the resource service application center station may also perform scaling or capacity expansion according to the request traffic state, that is, increase or decrease the resource service application center station instance. Specifically, the method may include:
a global monitoring platform (GloablMonitor) 104, configured to obtain execution state data of the resource service request matching the resource service application identifier in the resource service application identifier configuration library; and determining to expand or contract the capacity of the resource service application middlebox according to the execution state data. Specifically, the global monitoring platform 104 obtains, through the resource service application identifier in the resource service application identifier configuration library, a request execution state (which may also be understood as a load state) of the resource service application corresponding to the resource service application identifier, and when the request execution number is greater than or equal to the set expansion threshold, constructs a new resource service application middle station for the resource service application requesting service, and creates a thread group, where the created thread group may be a thread group that routes, to the thread group of the new resource service application middle station, the resource service request corresponding to the resource service application identifier whose load exceeds the expansion threshold, for which the request execution number is greater than or equal to the set expansion threshold. And if the execution number of the requests is greater than or equal to the set capacity reduction threshold, indicating that an idle thread group exists in the resource service application, releasing the idle thread group, thereby realizing the capacity reduction of the thread group.
The above is a description of an embodiment of a scheduling system for enterprise digital middlebox resource service applications provided by the present application, and on one hand, the scheduling system can route an acquired resource service request to a thread group corresponding to a resource service application identifier created according to a resource service application identifier list through a local monitoring platform, so that the resource service requests can all be processed in the corresponding thread group, and isolation of resource service request traffic of different resource service applications is achieved; on the other hand, according to the execution state data of the resource service request matched with the resource service application identifier in the resource service application identifier configuration library acquired by the global monitoring platform, the capacity expansion of the resource service application middle station or the capacity reduction of the thread group of the resource service application middle station can be realized, so that the resource waste is avoided, and the precise scheduling and adjustment of the resource service request are realized.
In order to facilitate understanding of the scheduling of the resource service request, the embodiment further includes: and the display device is used for displaying at least one of load state information of the thread group, resource service request quantity information corresponding to the current resource service application identifier, thread group information corresponding to the current resource service application identifier, thread quantity information of the thread group, request quantity information processed by the thread group, idle state information of the thread group, release information of the thread group and capacity expansion information of a middle station of the resource service application on an interface.
Based on the above, the present application further provides a method for scheduling resource service applications in an enterprise digital middlebox, as shown in fig. 2, fig. 2 is a flowchart of an embodiment of the method for scheduling resource service applications in an enterprise digital middlebox provided by the present application, where the local monitoring platform is taken as an angle, and the embodiment of the scheduling method is mainly described with the local monitoring platform in the embodiment of the scheduling system as an angle, and specifically may include:
step S201: creating a thread group which is positioned in a resource service application middle station and corresponds to the resource service application identifier according to the acquired resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene.
In this embodiment, the resource service application identifier in step S201 is used to describe participation identity information of the resource service application in a resource service application scenario. The resource service application may be various types of application services, such as: living, shopping, medicine, etc. The resource service may be, for example: and the functional services comprise commodity information inquiry, commodity state management, order inquiry service and the like. The resource service application identifier may be understood as identification information characterizing the resource service application, which may also be referred to as identity information, where the identity information may refer to a participation identity of an application service in an application scenario and is an independent business unit of a station performing a working capability in the resource service application. Invoking authentication for capability access and routing policy implemented by the extension point. The resource service application identification list may also be referred to as a resource service identity configuration list, which stores a list of resource service application identity information.
In this embodiment, the resource service application middlebox may be constructed by an enterprise digital middlebox. The thread groups may include at least two thread group groups 1 and 2. When creating a thread group, each resource service application identifier may correspond to a thread group, or multiple resource service application identifiers may correspond to a thread group.
In this embodiment, the specific implementation process of step S201 may include:
step S201-1: responding to a starting event of the resource service application middle station, and acquiring a resource service application identifier list for storing the resource service application identifier; the start event may be a trigger for a station in a resource service application.
Step S201-2: according to the resource service application identifier list, creating the thread group corresponding to the resource service application identifier; the creating mode may be that the same resource service application identifier corresponds to one thread group, and/or that a plurality of different resource service application identifiers correspond to one thread group. Namely, the thread group corresponding to the resource service application identifier is created, and the resource service request corresponding to the resource service application identifier can be scheduled to the corresponding thread group for execution when the subsequent resource service request is scheduled, so that the resource service request is isolated by the resource service application middlebox.
Step S202: and acquiring a resource service request of a station in the resource service application.
In this embodiment, a specific implementation process of the step S202 may be that a resource service request initiated by a terminal device is transmitted to the resource service application center, where the resource service request may be a request for one or more of the resource service application 1, the resource service application 2, and the resource service application 3, and the resource service request for each resource service application may be one or more request contents, such as an access request, an order request, a payment request, and the like.
Step S203: routing the resource service request to the thread group matched with the resource service application identification; wherein the thread group can execute the resource service request identified by one or more same resource service applications.
Step S203 may be understood as reading the resource service application identifier when the resource service application middleware is started, and then creating a corresponding thread group for the resource service application identifier, that is, the thread group1 corresponds to the resource service application 1, the thread group2 corresponds to the resource service application 2, the thread group 3 corresponds to the resource service application 3, and the thread group 4 corresponds to the resource service application 4. Thread group1, thread group2, thread group 3, and thread group 4 constitute a thread group set. And acquiring resource service requests initiated by the resource service application 1, the resource service application 2, the resource service application 3, the resource service application 4 and the like, and routing the request 1 in the resource requests to the thread group1 according to the resource service application identifier, wherein the request 2 is routed to the thread group2, the request 3 is routed to the thread group 3, and the request 4 is routed to the thread group 4, so that the requests 1 to 4 are all executed in respective matched thread groups, and are independent from each other, and flow isolation is realized. Of course, according to the state of the actual request traffic, the resource service requests identified by different resource service applications may also be routed to the same thread group, because, under the condition that the request traffic is small, the influence between the resource service applications may be negligible, or the generated influence does not relate to the running state between the resource service applications, and the waste of resources can also be reduced.
Based on the above, in order to avoid resource waste. The embodiment may further include:
acquiring execution state data of the thread group for executing the resource service request; the execution state data may include: request traffic handling data corresponding to resource service application identity information, for example: query Per Second (QPS), latency rate, throughput, etc.
Expanding the capacity of the resource service application middlebox or reducing the capacity of the thread group according to the execution state data; specifically, for example: when the query rate and/or the delay rate are/is large, it indicates that the request flow is large or in a saturated state, capacity expansion needs to be performed on the resource service application middlebox, otherwise, it indicates that the thread group is idle, and capacity reduction, that is, release, can be performed.
Correspondingly, this embodiment may further include: and displaying at least one of load state information of the thread group, resource service request quantity information corresponding to the current resource service application identifier, thread group information corresponding to the current resource service application identifier, thread quantity information of the thread group, request quantity information processed by the thread group, idle state information of the thread group, release information of the thread group and capacity expansion information of a central station of the resource service application.
The foregoing is a description of an embodiment of a scheduling method for an enterprise digital middlebox resource service application provided by the present application, and a difference between the embodiment of the scheduling method and the embodiment of the scheduling system is that the embodiment of the scheduling method takes a local monitoring platform of the embodiment of the scheduling system as a starting point for description, and therefore, for specific contents of the embodiment of the scheduling method, reference may be made to contents related to the local monitoring platform in the embodiment of the scheduling system, and details are not repeated here.
The foregoing is a detailed description of an embodiment of a scheduling method for an enterprise digital center resource service application provided by the present application, and corresponds to the foregoing embodiment of a scheduling method for an enterprise digital center resource service application, and the present application further discloses an embodiment of a scheduling apparatus for an enterprise digital center resource service application, please refer to fig. 3. The device embodiments described below are merely illustrative.
As shown in fig. 3, fig. 3 is a schematic structural diagram of an embodiment of a scheduling apparatus for an enterprise digital middlebox resource service application, which is provided by the present application and is from the perspective of a local monitoring platform; the embodiment of the scheduling device comprises:
a first obtaining unit 301, configured to create, according to an obtained resource service application identifier, a thread group located in a resource service application middleware and corresponding to the resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene.
The first obtaining unit 301 may include: a list acquisition subunit and a creation subunit; the list acquiring subunit is configured to acquire, in response to a start event of the resource service application middlebox, a resource service application identifier list for storing the resource service application identifier; and the creating subunit is configured to create the thread group corresponding to the resource service application identifier according to the resource service application identifier list.
A second obtaining unit 302, configured to obtain a resource service request of a resource service application;
a routing unit 303, configured to route the resource service request to the thread group that matches the resource service application identifier; wherein the thread group executes the resource service requests identified by one or more same resource service applications.
In some embodiments, it may further include: the data acquisition unit is used for acquiring execution state data of the thread group executing the resource service request; and the processing unit is used for carrying out capacity expansion or capacity reduction processing on the thread group according to the execution state data.
In some embodiments, it may further include: a sending unit, configured to send the execution state data to the resource service application identifier list.
In some embodiments, it may further include: and the display unit is used for displaying at least one of load state information of the thread group, resource service request quantity information corresponding to the current resource service application identifier, thread group information corresponding to the current resource service application identifier, thread quantity information of the thread group, request quantity information processed by the thread group, idle state information of the thread group, release information of the thread group and capacity expansion information of a middle platform of the resource service application on an interface.
The above is a description of an embodiment of a scheduling apparatus for resource service application in an enterprise digital middlebox, and the contents of the scheduling apparatus embodiment may refer to the relevant contents of the scheduling system embodiment and the scheduling method embodiment of the resource service application in the enterprise digital middlebox, which are not repeated herein.
Based on the above, the present application further provides a method for scheduling resource service applications in an enterprise digital middlebox, as shown in fig. 4, where fig. 4 is a flowchart of an embodiment of the method for scheduling resource service applications in an enterprise digital middlebox provided by the present application, where the global monitoring platform is taken as an angle, and the embodiment of the scheduling method is mainly described with the global monitoring platform in the embodiment of the scheduling system as an angle, and specifically may include:
step S401: acquiring resource service request execution state data of the resource service application identifier in a resource service application identifier list; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene.
The resource service request execution state data in step S401 may be uploaded to the resource service application identifier library through the local monitoring platform, and may include: request traffic handling data corresponding to resource service application identity information, for example: query Per Second (QPS), latency rate, throughput, etc. Reference may be made specifically to the description of the scheduling system embodiments described above.
Step S402: according to the resource service request execution state, carrying out capacity expansion or capacity reduction on a resource service application center; the resource service application middle station comprises a thread group which is established according to the acquired resource service application identifier, is positioned in the resource service application middle station and corresponds to the resource service application identifier. For example: and when the request execution quantity is greater than or equal to the set capacity expansion threshold, constructing a new resource service application middle station for the resource service application requesting service. And when the execution quantity of the requests is greater than or equal to the set capacity reduction threshold, combining all the requests in the resource service application middle station corresponding to the request service to other resource service application middle stations and releasing the requests, thereby realizing the capacity reduction of the resource service application middle stations. Reference may be made specifically to the description of the scheduling system embodiments described above.
The above is a description of an embodiment of a scheduling method for resource service application in enterprise digital middleboxes provided by the present application, and corresponds to the foregoing embodiment of a scheduling method for resource service application in enterprise digital middleboxes provided by the present application, and the present application further discloses an embodiment of a scheduling apparatus for resource service application in enterprise digital middleboxes, please refer to fig. 5, since the apparatus embodiment is basically similar to the method embodiment, the description is relatively simple, and related points can be referred to part of the description of the method embodiment. The device embodiments described below are merely illustrative.
As shown in fig. 5, fig. 5 is a schematic structural diagram of an embodiment of a scheduling apparatus for resource service application in an enterprise digital middlebox from the perspective of a global monitoring platform, where the embodiment of the scheduling apparatus includes:
an obtaining unit 501, configured to obtain a resource service request execution state of a resource service application identifier in a resource service application identifier list; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
a processing unit 502, configured to perform capacity expansion or capacity reduction on a resource service application middlebox according to the resource service request execution state; the resource service application middle station comprises a thread group which is established according to the acquired resource service application identifier, is positioned in the resource service application middle station and corresponds to the resource service application identifier.
For specific implementation processes of the obtaining unit 501 and the processing unit 502, reference may be made to the contents of the scheduling system embodiment and the contents of step S401 to step S402, and details are not repeated here.
Based on the above content, the present application further provides a scheduling method for resource service applications in an enterprise digital middlebox, as shown in fig. 6, fig. 6 is a flowchart of an embodiment of the scheduling method for resource service applications in an enterprise digital middlebox, which is provided by the present application, with a local and global monitoring platform as an angle, where the embodiment of the scheduling method is described in multiple angles, that is: the method comprises a first-level scheduling and a second-level scheduling, wherein the first-level scheduling corresponds to a local monitoring platform in a scheduling system embodiment, and the second-level scheduling corresponds to a global monitoring platform in a scheduling system. The specific implementation process of the scheduling method embodiment may include:
step S601: the local monitoring platform establishes a thread group which is positioned in a resource service application middle station and corresponds to the resource service application identifier according to the acquired resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
step S602: the local monitoring platform acquires a resource service request of a resource service application center; the local monitoring platform corresponds to the resource service application middle platform;
step S603: the local monitoring platform routes the resource service request to the thread group matched with the resource service application identifier; wherein the thread group executes the resource service requests identified by one or more same resource service applications;
step S604: responding to the resource service request execution state of the resource service application identifier in the resource service application identifier list sent by the local monitoring platform by the global monitoring platform, and performing capacity expansion or capacity reduction on the resource service application middlebox.
For the specific content of the above steps S601 to S604, reference may be made to the content of the above scheduling system embodiment, and a repeated description of corresponding or same content is not repeated here.
Based on the foregoing, the present application further provides a scheduling apparatus for resource service application in an enterprise digital middlebox, as shown in fig. 7, fig. 7 is a schematic structural diagram of an embodiment of the scheduling apparatus for resource service application in an enterprise digital middlebox, which is provided by the present application, with a local monitoring platform and a global monitoring platform as an angle, where the embodiment of the scheduling apparatus includes:
a creating unit 701, configured to create, by a local monitoring platform, a thread group, which is located in a resource service application middleware and corresponds to a resource service application identifier, according to an obtained resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
an obtaining unit 702, configured to obtain, by the local monitoring platform, a resource service request of a resource service application center; the local monitoring platform corresponds to the resource service application middlebox;
a routing unit 703, configured to route, by the local monitoring platform, the resource service request to the thread group that matches the resource service application identifier; wherein the thread group executes the resource service requests identified by one or more same resource service applications;
a processing unit 704, configured to respond, by the global monitoring platform, to the resource service request execution state of the resource service application identifier sent by the local monitoring platform, in the resource service application identifier list, and perform capacity expansion or capacity reduction on the resource service application middlebox.
Based on the above, the present application further provides a computer storage medium for storing data generated by a network platform and a program for processing the data generated by the network platform;
when being read and executed by a processor, the program executes the contents of the steps S201 to S203 in the embodiment of the scheduling method of the resource service application in the enterprise digital center as described above; or, the contents of step S401 to step S402 in the embodiment of the scheduling method for resource service application in the enterprise digital middlebox as described above are executed; alternatively, the contents of step S601 to step S604 in the embodiment of the scheduling method for resource service application in the enterprise digital center are executed as described above.
Based on the above, the present application further provides an electronic device, as shown in fig. 8, where the embodiment of the electronic device includes:
a processor 801;
a memory 802 for storing a program for processing data generated by the network platform, wherein the program, when being read and executed by the processor, executes the contents of steps S201 to S203 in the embodiment of the scheduling method for resource service application in the enterprise digital middlebox as described above; or, the contents of step S401 to step S402 in the embodiment of the scheduling method for resource service application in the enterprise digital middlebox as described above are executed; alternatively, the contents of step S601 to step S604 in the embodiment of the scheduling method for resource service application in the enterprise digital center are executed as described above.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
1. Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.
Claims (14)
1. A system for scheduling resource service applications in an enterprise digital middlebox, comprising: the resource service application identifier configuration library is positioned in the enterprise digital center, the resource service application center and a local monitoring platform corresponding to the resource service application center;
the resource service application identifier configuration library is used for storing a resource service application identifier list of resource service application identifiers; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
and the local monitoring platform acquires a plurality of resource service requests of the resource service application middle station, respectively routes the resource service requests to a thread group corresponding to the resource service application identification and created according to the resource service application identification list.
2. The system according to claim 1, wherein the local monitoring platform obtains the resource service application identifier list in the resource service application identifier configuration library, and creates the thread group corresponding to the resource service application identifier according to the resource service application identifier in the resource service application identifier list.
3. The system of claim 1, wherein the local monitoring platform obtains execution status data of the thread group executing the resource service request; and carrying out capacity expansion or capacity reduction on the thread group according to the execution state data.
4. The system of claim 3, wherein the resource service application identification configuration repository further stores execution state data for the thread group to execute the resource service request.
5. The system of claim 1, further comprising: the global monitoring platform is used for acquiring execution state data of the resource service request matched with the resource service application identifier in the resource service application identifier configuration library; and determining to perform capacity expansion or capacity reduction on the resource service application middlings according to the execution state data.
6. The system for scheduling resource services applications in an enterprise digital center according to claim 1, further comprising:
and the display device is used for displaying at least one of load state information of the thread group, resource service request quantity information corresponding to the current resource service application identifier, thread group information corresponding to the current resource service application identifier, thread quantity information of the thread group, request quantity information processed by the thread group, idle state information of the thread group, release information of the thread group and capacity expansion information of a middle station of the resource service application on an interface.
7. A method for scheduling resource service application in an enterprise digital middlebox is characterized by comprising the following steps:
creating a thread group which is positioned in a resource service application middle station and corresponds to the resource service application identifier according to the acquired resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
acquiring a plurality of resource service requests of a resource service application center;
and according to the resource service application identification, respectively routing the resource service requests to the thread groups matched with the resource service application identification.
8. The method according to claim 7, wherein the creating a thread group corresponding to the resource service identifier in the resource service application middlebox according to the obtained resource service application identifier comprises:
responding to a starting event of the resource service application middle station, and acquiring a resource service application identifier list for storing the resource service application identifier;
and creating the thread group corresponding to the resource service application identifier according to the resource service application identifier list.
9. The method of claim 7, further comprising:
acquiring execution state data of the thread group for executing the resource service request;
and carrying out capacity expansion or capacity reduction on the thread group according to the execution state data.
10. The method of claim 9, further comprising:
and sending the execution state data to the resource service application identification list.
11. A method for scheduling resource service application in an enterprise digital middlebox is characterized by comprising the following steps:
acquiring a resource service request execution state of the resource service application identifier in a resource service application identifier list; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
according to the resource service request execution state, carrying out capacity expansion or capacity reduction on the resource service application middlebox; the resource service application middle station comprises a thread group which is established according to the acquired resource service application identifier, is positioned in the resource service application middle station and corresponds to the resource service application identifier.
12. A method for scheduling resource service application in an enterprise digital middlebox is characterized by comprising the following steps:
the local monitoring platform establishes a thread group which is positioned in a resource service application middle station and corresponds to the resource service application identifier according to the acquired resource service application identifier; the resource service application identifier is used for describing participation identity information of the resource service application in a resource service application scene;
the local monitoring platform acquires a plurality of resource service requests of a resource service application center; the local monitoring platform corresponds to the resource service application middlebox;
the local monitoring platform routes the resource service requests to the thread groups matched with the resource service application identifications according to the resource service application identifications respectively;
responding to the resource service request execution state of the resource service application identifier in the resource service application identifier list sent by the local monitoring platform by the global monitoring platform, and performing capacity expansion or capacity reduction on the resource service application middlebox.
13. A computer storage medium for storing network platform generated data and a program for processing the network platform generated data;
the program, when read and executed by a processor, performs a method of scheduling resource service applications in an enterprise digital center as claimed in any one of claims 7-10; or, performing the method of scheduling resource service applications in an enterprise digital center as claimed in claim 11; or to perform the method of scheduling resource service applications in an enterprise digital center as claimed in claim 12 above.
14. An electronic device, comprising:
a processor;
a memory for storing a program for processing data generated by a network platform, the program, when read and executed by the processor, executing the method for scheduling resource service applications in an enterprise digital central station according to any one of claims 7 to 10; or, performing the method of scheduling resource service applications in an enterprise digital center as claimed in claim 11; or to perform the method of scheduling resource service applications in an enterprise digital center as claimed in claim 12 above.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210006017.2A CN114036031B (en) | 2022-01-05 | 2022-01-05 | Scheduling system and method for resource service application in enterprise digital middleboxes |
| PCT/CN2022/143628 WO2023131058A1 (en) | 2022-01-05 | 2022-12-29 | System and method for scheduling resource service application in digital middle office of enterprise |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210006017.2A CN114036031B (en) | 2022-01-05 | 2022-01-05 | Scheduling system and method for resource service application in enterprise digital middleboxes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114036031A CN114036031A (en) | 2022-02-11 |
| CN114036031B true CN114036031B (en) | 2022-06-24 |
Family
ID=80147291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210006017.2A Active CN114036031B (en) | 2022-01-05 | 2022-01-05 | Scheduling system and method for resource service application in enterprise digital middleboxes |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114036031B (en) |
| WO (1) | WO2023131058A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114036031B (en) * | 2022-01-05 | 2022-06-24 | 阿里云计算有限公司 | Scheduling system and method for resource service application in enterprise digital middleboxes |
| CN116700907B (en) * | 2023-08-04 | 2023-10-27 | 北京国电通网络技术有限公司 | Service call demand document storage method, device, electronic equipment and readable medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111984709A (en) * | 2019-05-23 | 2020-11-24 | 云南青年学园科技有限公司 | Visual big data middle station-resource calling and algorithm |
| CN112328656A (en) * | 2020-11-02 | 2021-02-05 | 中国平安财产保险股份有限公司 | Service query method, device, equipment and storage medium based on middle platform architecture |
| CN113595926A (en) * | 2021-07-28 | 2021-11-02 | 南方电网数字电网研究院有限公司 | API data transmission method, device, equipment and medium based on data middlebox |
| WO2021258340A1 (en) * | 2020-06-24 | 2021-12-30 | 京东方科技集团股份有限公司 | Publishing system, pushing method, application device, receiving apparatus, and service management device |
Family Cites Families (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1602034A2 (en) * | 2003-03-11 | 2005-12-07 | GTV Solutions Inc. | Communications interchange system |
| EP1646188B2 (en) * | 2003-06-20 | 2018-10-03 | ZTE Corporation | A method for ethernet network service safety isolation |
| US7953916B2 (en) * | 2009-04-08 | 2011-05-31 | Intel Corporation | Dynamic, local retriggered interrupt routing discovery method |
| CN102789394B (en) * | 2011-05-19 | 2014-12-24 | 阿里巴巴集团控股有限公司 | Method, device and nodes for parallelly processing information and server cluster |
| US20130110588A1 (en) * | 2011-10-26 | 2013-05-02 | Iex Corporation | Application usage and process monitoring in an enterprise environment |
| CN109582472B (en) * | 2018-10-19 | 2021-05-18 | 华为技术有限公司 | Micro-service processing method and device |
| US11003566B2 (en) * | 2018-12-31 | 2021-05-11 | Paypal, Inc. | Tracking data flow through data services using a processing request identifier in callstack data |
| CN110324403A (en) * | 2019-05-23 | 2019-10-11 | 平安科技（深圳）有限公司 | Dynamic divides library method for routing, device, server and storage medium |
| TWM592136U (en) * | 2019-10-21 | 2020-03-11 | 臺灣銀行股份有限公司 | Webpage navigation intermediary system |
| CN111343275B (en) * | 2020-03-02 | 2022-09-30 | 北京奇艺世纪科技有限公司 | Resource scheduling method and system |
| CN111614570B (en) * | 2020-04-20 | 2022-07-01 | 北京邮电大学 | Flow control system and method for service grid |
| CN111629061B (en) * | 2020-05-28 | 2023-01-24 | 苏州浪潮智能科技有限公司 | Inference service system based on Kubernetes |
| CN111738757A (en) * | 2020-06-15 | 2020-10-02 | 中国建设银行股份有限公司 | Multi-channel service platform |
| CN111736977B (en) * | 2020-07-21 | 2020-11-10 | 成都新希望金融信息有限公司 | Central dispatching method and system for multiple middle stations |
| CN112036723A (en) * | 2020-08-24 | 2020-12-04 | 北京金成顺赢互联网科技有限公司 | Enterprise digital collaborative operation middle platform |
| CN112015521B (en) * | 2020-09-30 | 2024-06-07 | 北京百度网讯科技有限公司 | Configuration method and device of reasoning service, electronic equipment and storage medium |
| CN112199430A (en) * | 2020-10-15 | 2021-01-08 | 苏州龙盈软件开发有限公司 | Business data processing system and method based on data middling station |
| CN112559486A (en) * | 2020-11-11 | 2021-03-26 | 国网江苏省电力有限公司信息通信分公司 | Data center unified task scheduling management system |
| CN113392158A (en) * | 2021-06-11 | 2021-09-14 | 中国工商银行股份有限公司 | Service data processing method and device and data center |
| CN113472771B (en) * | 2021-06-29 | 2023-03-24 | 福建华通银行股份有限公司 | Intelligent middle platform system |
| CN113806097B (en) * | 2021-09-29 | 2024-08-09 | 杭州网易云音乐科技有限公司 | Data processing method, device, electronic equipment and storage medium |
| CN113868110B (en) * | 2021-11-30 | 2022-07-12 | 阿里云计算有限公司 | Method and device for evaluating health degree of enterprise digital center service |
| CN114036031B (en) * | 2022-01-05 | 2022-06-24 | 阿里云计算有限公司 | Scheduling system and method for resource service application in enterprise digital middleboxes |
-
2022
- 2022-01-05 CN CN202210006017.2A patent/CN114036031B/en active Active
- 2022-12-29 WO PCT/CN2022/143628 patent/WO2023131058A1/en unknown
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111984709A (en) * | 2019-05-23 | 2020-11-24 | 云南青年学园科技有限公司 | Visual big data middle station-resource calling and algorithm |
| WO2021258340A1 (en) * | 2020-06-24 | 2021-12-30 | 京东方科技集团股份有限公司 | Publishing system, pushing method, application device, receiving apparatus, and service management device |
| CN112328656A (en) * | 2020-11-02 | 2021-02-05 | 中国平安财产保险股份有限公司 | Service query method, device, equipment and storage medium based on middle platform architecture |
| CN113595926A (en) * | 2021-07-28 | 2021-11-02 | 南方电网数字电网研究院有限公司 | API data transmission method, device, equipment and medium based on data middlebox |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023131058A1 (en) | 2023-07-13 |
| CN114036031A (en) | 2022-02-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11159411B2 (en) | Distributed testing service | |
| US10831562B2 (en) | Method and system for operating a data center by reducing an amount of data to be processed | |
| US9607019B1 (en) | Splitting database partitions | |
| CN114036031B (en) | Scheduling system and method for resource service application in enterprise digital middleboxes | |
| CN109032803B (en) | Data processing method and device and client | |
| CN103368986A (en) | Information recommendation method and information recommendation device | |
| CN112769671B (en) | Message processing method, device and system | |
| CN106302640A (en) | Data request processing method and device | |
| US11563805B2 (en) | Method, apparatus, client terminal, and server for data processing | |
| CN102882960B (en) | A kind of sending method of resource file and device | |
| CN110764930A (en) | Request or response processing method and device based on message mode | |
| CN114020444A (en) | Calling system and method for resource service application in enterprise digital middleboxes | |
| CN111464574B (en) | Calling, loading, registering and managing method and route, server, node and medium | |
| CN117692401A (en) | Message sending method, device, server and storage medium | |
| CN106899652B (en) | Method and device for pushing service processing result | |
| CN111221858B (en) | Data processing method, device and equipment | |
| CN108900593B (en) | Distributed processing method for data of storage cabinet | |
| CN112328598A (en) | ID generation method, device, electronic equipment and storage medium | |
| US9456024B1 (en) | Content sharing in mobile ad hoc networks | |
| CN111694611B (en) | Data processing method and device and electronic equipment | |
| CN116501383B (en) | Micro-service distribution method and device, electronic equipment and readable storage medium | |
| CN116170501B (en) | Processing method and device of network task, server and storage medium | |
| US11394780B2 (en) | System and method for facilitating deduplication of operations to be performed | |
| CN115757387A (en) | Correlation integration and rapid retrieval method supporting multi-source heterogeneous data | |
| CN117271596A (en) | Message processing method and device |
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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40067484 Country of ref document: HK |