WO2023131058A1 - 一种企业数字中台中资源服务应用的调度系统和方法 - Google Patents
一种企业数字中台中资源服务应用的调度系统和方法 Download PDFInfo
- Publication number
- WO2023131058A1 WO2023131058A1 PCT/CN2022/143628 CN2022143628W WO2023131058A1 WO 2023131058 A1 WO2023131058 A1 WO 2023131058A1 CN 2022143628 W CN2022143628 W CN 2022143628W WO 2023131058 A1 WO2023131058 A1 WO 2023131058A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource service
- service application
- platform
- thread group
- resource
- Prior art date
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
Definitions
- the present application relates to the field of computer technology, in particular to a scheduling system and method for Taichung resource service applications in enterprise digital.
- the present application relates to a computer storage medium and an electronic device at the same time.
- Digital transformation is based on digital transformation (Digitization) and digital upgrade (Digitalization), which can touch the core business of the enterprise and establish a transformation with the goal of business operation model.
- the digital middle platform of the operating system has become an effective system form and organizational method for enterprises to carry out digital transformation, so that enterprises can conduct business exploration and innovation more efficiently, and realize the construction of enterprise core differentiated competitiveness in the form of digital assets.
- the present application provides a scheduling system and method for resource service application in an enterprise digital platform to solve the problem of inflexible isolation of request flow in the platform and waste of resources in the prior art.
- This application provides a scheduling system for resource service applications in an enterprise digital platform, including: a resource service application identification configuration library located in the enterprise digital platform, a resource service application platform, and a resource service application platform corresponding to the resource service application platform Local monitoring platform;
- the resource service application identification configuration library is used to store the resource service application identification list of the resource service application identification; wherein, the resource service application identification is used to describe the participation identity information of the resource service application in the resource service application scenario;
- the local monitoring platform acquires multiple resource service requests from the platform in the resource service application, and routes the multiple resource service requests to, respectively, the resource service application identifier created according to the resource service application identifier list. in the corresponding thread group.
- the local monitoring platform obtains the resource service application identification list in the resource service application identification configuration library, and creates a The thread group corresponding to the service application identifier.
- the local monitoring platform obtains the execution state data of the resource service request executed by the thread group; expands or shrinks the thread group according to the execution state data.
- the resource service application identification configuration library also stores execution status data of the thread group executing the resource service request.
- it further includes: a global monitoring platform, configured to obtain the execution status data of the resource service request matching the resource service application ID in the resource service application ID configuration library; according to the execution status data , determining to expand or shrink the capacity of the plurality of resource service application centers.
- a global monitoring platform configured to obtain the execution status data of the resource service request matching the resource service application ID in the resource service application ID configuration library; according to the execution status data , determining to expand or shrink the capacity of the plurality of resource service application centers.
- a display device configured to display on the interface the load status information of the thread group, the resource service request quantity information corresponding to the current resource service application identifier, the thread group information corresponding to the current resource service application identifier, and the threads of the thread group At least one of quantity information, request volume information processed by the thread group, idle state information of the thread group, release information of the thread group, and capacity expansion information of the platform in the resource service application.
- the present application also provides a scheduling method for Taichung resource service application in the enterprise digital center, including:
- the creation of a thread group corresponding to the resource service identifier located in the resource service application platform according to the obtained resource service application identifier includes:
- the present application also provides a scheduling method for Taichung resource service application in the enterprise digital center, including:
- the resource service application platform includes a platform located in the resource service application platform created according to the obtained resource service application identifier, A thread group corresponding to the resource service application identifier.
- the present application also provides a scheduling method for Taichung resource service application in the enterprise digital center, including:
- the local monitoring platform creates a thread group corresponding to the resource service application identifier located in the resource service application platform according to the obtained resource service application identifier; wherein, the resource service application identifier is used to describe the resources in the resource service application scenario Participation identity information for service applications;
- the local monitoring platform obtains multiple resource service requests from the resource service application platform; wherein, the local monitoring platform corresponds to the resource service application platform;
- the local monitoring platform routes the plurality of resource service requests respectively to the thread group matching the resource service application identifier
- the global monitoring platform expands or shrinks the capacity of the resource service application middle platform in response to the resource service request execution status sent by the local monitoring platform to the resource service application identification in the resource service application identification list.
- the present application also provides a computer storage medium for storing data generated by the network platform, and a program for processing the data generated by the network platform;
- the present application also provides an electronic device, including:
- the memory is used to store the program for processing the data generated by the network platform.
- the program When the program is read and executed by the processor, it executes the scheduling method of the resource service application in the platform of the enterprise digital center as described above; or executes the above method The above-mentioned method for scheduling resource service applications in Taichung Enterprise Digital Center; or, execute the method for scheduling resource service applications in Taichung Enterprise Digital Center as described above.
- the application provides a scheduling system and method for resource service applications in enterprise digital platforms.
- the resource service requests obtained can be routed through the local monitoring platform, and the resource service applications created according to the resource service application identification list Identify the corresponding thread group, so that resource service requests can be processed in the corresponding thread group, and realize the north-south isolation of resource service request traffic of different resource service applications;
- resource service applications can be obtained according to the global monitoring platform Identify the execution status data of the resource service request in the configuration library that matches the resource service application identifier, and realize the expansion or contraction of the platform in the resource service application, thereby avoiding resource waste and realizing precise scheduling and adjustment of resource service requests .
- FIG. 1 is a schematic structural diagram of an embodiment of a scheduling system for resource service applications in an enterprise digital center provided by the present application;
- FIG. 2 is a flow chart of an embodiment from the perspective of a local monitoring platform in a scheduling method for resource service applications in Taichung in an enterprise digital center provided by the present application;
- FIG. 3 is a schematic structural diagram of an embodiment from the perspective of a local monitoring platform in a scheduling device for resource service applications in Taichung in an enterprise digital center provided by the present application;
- FIG. 4 is a flow chart of an embodiment from the perspective of the global monitoring platform in a scheduling method for resource service applications in Taichung in the enterprise digital center provided by the present application;
- FIG. 5 is a schematic structural diagram of an embodiment from the perspective of a global monitoring platform in a scheduling device for resource service applications in an enterprise digital center provided by the present application;
- FIG. 6 is a flow chart of an embodiment from the perspective of local and global monitoring platforms in a scheduling method for resource service applications in Taichung in an enterprise digital center provided by the present application;
- Fig. 7 is a schematic structural diagram of an embodiment in terms of local and global monitoring platforms in a scheduling device for resource service applications in Taichung in the digital enterprise provided by the application;
- Fig. 8 is a schematic structural diagram of an embodiment of an electronic device provided by the present application.
- the enterprise digital middle platform is a business-oriented capability combination, sharing and reuse, and provides an integrated solution with the purpose of improving R&D efficiency and reducing innovation costs.
- the enterprise digital middle platform may include users, combinations, platforms, data, standards, and norms, and is an overall system of users and systems. That is: the enterprise digital middle platform is an enterprise-level capability reuse platform that abstracts the common needs of enterprises and builds them into platform-based and component-based system capabilities, which are shared by various business units in the form of interfaces and components.
- the enterprise digital center will provide services for each application in a shared manner, so the application service becomes one of the key entities in the enterprise digital center.
- the non-interference between various application services is one of the important factors for the normal operation of the enterprise digital center.
- the existing traffic isolation between various application services in the enterprise digital center usually adopts physical isolation.
- the method is to deploy different application instances in the middle platform for different application services, so as to realize the isolation of application service traffic in the north-south direction of the enterprise digital middle platform.
- the problems of this physical isolation method are as follows:
- this application proposes to provide a scheduling system and method for resource service applications in enterprise digital platforms, which can solve the problems of inflexibility and waste of resources in manual deployment of central platform application instances.
- the following will describe the enterprise digital platform resource services provided by this application
- the application scheduling system and method are described in detail.
- Figure 1 is a schematic structural diagram of an embodiment of a scheduling system for resource service applications in an enterprise digital center provided by the present application;
- the embodiment of the scheduling system includes: a resource service application identification configuration library 101, an enterprise digital center platform The resource service application middle platform 102, and the local monitoring platform (Local Monitor) 103 corresponding to the resource service application middle platform;
- the resource service application identification configuration library 101 is used to store a resource service application identification list of resource service application identifications; wherein, the resource service application identifications are used to describe participation identity information of resource service application in resource service application scenarios. It can also be called business identity, which can refer to the participating identity of application services in application scenarios, and is an independent business unit with the ability to perform work in resource service applications. Call authentication for capability access and routing strategies implemented by extension points.
- the service identity may be the level of the resource service application. There may be multiple resource service applications for the same user, and different resource service applications may have different identity levels, or may belong to the same identity level.
- the identity level of the resource service application may also include a sub-identity level, that is, an identity level capable of distinguishing the overall link of the resource service application. For example: application 1 is a first-level service identity, application 2 is also a first-level service identity, and application 3 is a second-level service identity subordinate to application 1.
- the resource service application may be various application services, such as application services for life, shopping, and medicine.
- Resource services can be, for example, functional services such as product information query, product status management, and order query service.
- the resource service application identification list may also be referred to as a resource service identity configuration list, which stores resource service application identity information.
- the resource service identity configuration list can also be stored, and the traffic processing data corresponding to the resource service application identity information transmitted by the local monitoring platform 103, for example: query rate per second (QPS, Queries-per-second), delay rate, throughput, etc.
- the local monitoring platform 103 acquires the resource service request of the resource service application platform 102, and routes the resource service request to the thread corresponding to the resource service application identifier created according to the resource service application identifier list In the group; wherein, the thread group executes one or more resource service requests identified by the same resource service application.
- the resource service application center 102 can be constructed through an enterprise digital center.
- the local monitoring platform 103 obtains the resource service application identifier list in the resource service application identifier configuration library 101, and creates a resource service application identifier corresponding to the resource service application identifier according to the resource service application identifier in the resource service application identifier list.
- the local monitoring platform 103 reads the resource service application identification list in the resource service application identification configuration library 101 when the resource service application middle platform 102 starts.
- 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 will be transmitted to the resource service application center 102, and the resource service application center 102 will respectively route the resource service request to the thread group according to the resource service application identifier.
- resource service application identifiers of resource service application 1 , resource service application 2 , resource service application 3 , and resource service application 4 are stored in the resource service application identifier configuration library 101 .
- the resource service request may be a request for one or more applications in 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 access requests, order requests, payment requests, etc.
- the local monitoring platform will read the identification in the resource service application identification configuration library, and then create a corresponding thread group for the resource service application identification, that is, thread group 1 corresponds to the resource service request of resource service application 1 , thread group 2 corresponds to the resource service request of resource service application 2, thread group 3 corresponds to the resource service request of resource service application 3, and thread group 4 corresponds to the resource service request of resource service application 4.
- Thread group 1, thread group 2, thread group 3 and thread group 4 may constitute a thread group set.
- the resource service request initiated to the resource service application 1, resource service application 2, resource service application 3, resource service application 4, etc. will first be transmitted to the local monitoring platform 103, and the local monitoring platform 103 will resource service application identification according to the resource service application Service request 1 is routed to thread group 1, the reason for request 2 is routed to thread group 2, request 3 is routed to thread group 3, and request 4 is routed to thread group 4, so that requests 1 to 4 are independent of each other and traffic isolation is achieved.
- resource service requests identified by different resource service applications can also be routed to the same thread group, thereby reducing resource waste, because, when the request traffic is small, resource service applications between The impact is negligible, or the impact does not involve the running status between resource service applications.
- the execution state data of the thread group executing the resource service request can be obtained through the local monitoring platform 103, and the thread group can be expanded or reduced according to the execution state data .
- the execution state data may include: request flow processing data corresponding to resource service application identity information, for example: query rate per second (QPS, Queries-per-second), delay rate, throughput, etc.
- QPS query rate per second
- delay rate delay rate
- throughput etc.
- the capacity of the resource service application center can also be reduced or expanded according to the request traffic status, that is, the resource service application center instance is increased or the resource service application center instance is reduced. Specifically, it may include:
- the global monitoring platform (GloablMonitor) 104 is used to obtain the execution status data of the resource service request matching the resource service application ID in the resource service application ID configuration library; Resource service application middle platform expands or shrinks capacity. Specifically, the global monitoring platform 104 acquires the request execution status (also can be understood as load status) of the resource service application corresponding to the resource service application identifier through the resource service application identifier in the resource service application identifier configuration library, when If the number of request executions is greater than or equal to the set expansion threshold, a new resource service application platform will be built for the resource service application requesting the service, and a thread group will be created.
- the expansion threshold of the corresponding resource service application ID can route the resource service request corresponding to the resource service application ID whose load exceeds the expansion threshold to the thread group of the new resource service application platform. If the number of request executions is greater than or equal to the set shrinkage threshold, it means that there is an idle thread group in the platform of the resource service application, and the idle thread group will be released to realize the shrinkage of the thread group.
- this embodiment of the scheduling system can route resource service requests obtained through a local monitoring platform, and according to the resource service application In the thread group corresponding to the resource service application identifier created by the identification list, so that all resource service requests can be processed in the corresponding thread group, realizing the isolation of resource service request traffic of different resource service applications; on the other hand, it can 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 platform in the resource service application or the thread of the platform in the resource service application are realized Group shrinkage, thereby avoiding resource waste, and realizing precise scheduling and adjustment of resource service requests.
- this embodiment also includes: a display device for displaying on the interface the load status information of the thread group, the resource service request quantity information corresponding to the current resource service application identifier, and the current resource service application ID.
- the service application identifier corresponds to the thread group information, the thread number information of the thread group, the request volume information processed by the thread group, the idle state information of the thread group, the release information of the thread group, and the resource At least one type of information in the platform expansion information in the service application.
- this application also provides a scheduling method for resource service applications in enterprise digital centers, as shown in Figure 2.
- Figure 2 is a scheduling method for resource service applications in enterprise digital centers that uses local monitoring
- the flow chart of the embodiment from the perspective of the platform, the embodiment of the scheduling method is mainly described from the perspective of the local monitoring platform in the embodiment of the scheduling system, which may specifically include:
- Step S201 Create a thread group corresponding to the resource service application identifier located in the resource service application platform according to the obtained resource service application identifier; wherein, the resource service application identifier is used to describe resources in the resource service application scenario Participating identity information for the service application.
- the resource service application identifier in step S201 is used to describe the participation identity information of the resource service application in the resource service application scenario.
- the resource service application may be various application services, such as: life, shopping, medicine and other application services.
- Resource services can be, for example, functional services such as product information query, product status management, and order query services.
- the resource service application identifier can be understood as the identification information that characterizes the resource service application, and can also be called identity information.
- the identity information can refer to the participating identity of the application service in the application scenario, and is an independent business of the platform's ability to perform work in the resource service application. unit. Call authentication for capability access and routing strategies implemented by extension points.
- the resource service application identification list may also be referred to as a resource service identity configuration list, which stores resource service application identity information.
- the resource service application center can be constructed through an enterprise digital center.
- the thread group may include at least two thread groups group1 and group2.
- each resource service application ID may correspond to a thread group, or multiple resource service application IDs may correspond to a thread group.
- step S201 may include:
- Step S201-1 Responding to a startup event of the resource service application platform, obtain a resource service application identifier list for storing the resource service application identifier; the startup event may be a trigger for the resource service application platform.
- Step S201-2 Create the thread group corresponding to the resource service application ID according to the resource service application ID list; the creation method may be that the same resource service application ID corresponds to a thread group, and/or , multiple different resource service application identifiers correspond to one thread group. That is, creating the thread group corresponding to the resource service application identifier can schedule the resource service request corresponding to the resource service application identifier to the corresponding thread group for execution during subsequent resource service request scheduling, thereby realizing the resource service application
- the middle platform isolates resource service requests.
- Step S202 Obtain a resource service request from a platform in the resource service application.
- step S202 may be that the resource service request initiated by the terminal device will be transmitted to the resource service application platform, and the resource service request may be for resource service application 1, resource service The request of one or more applications in application 2 and resource service application 3, the resource service request for each resource service application may be one or more request contents, such as access request, order request, payment request and so on.
- Step S203 Routing the resource service request to the thread group matching the resource service application identifier; wherein, the thread group can execute one or more resource services of the same resource service application identifier ask.
- the step S203 can be understood as, when the resource service application platform starts, read the resource service application ID, and then create a corresponding thread group for the resource service application ID, that is, thread group 1 corresponds to resource service application 1 and thread group 2 Corresponding to resource service application 2, thread group 3 resource service application 3 and thread group 4 resource service application 4. Thread group 1, thread group 2, thread group 3 and thread group 4 constitute a thread group set.
- resource service requests initiated by the resource service application 1, resource service application 2, resource service application 3, resource service application 4, etc. route request 1 in the resource request to thread group 1 according to the resource service application identifier, and the reason for request 2 To thread group 2, request 3 is routed to thread group 3, and request 4 is routed to thread group 4, so that requests 1 to 4 are executed in their respective matching thread groups, so they are independent of each other and traffic isolation is achieved.
- resource service requests identified by different resource service applications can also be routed to the same thread group, because, in the case of small request traffic, the impact between resource service applications is negligible , or the impact will not involve the running status between resource service applications, and can also reduce the waste of resources.
- This embodiment can also include:
- the execution status data may include: request traffic processing data corresponding to the resource service application identity information, for example: query rate per second (QPS, Queries-per- second), delay rate, throughput, etc.
- request traffic processing data corresponding to the resource service application identity information, for example: query rate per second (QPS, Queries-per- second), delay rate, throughput, etc.
- Expand the capacity of the resource service application center or shrink the thread group according to the execution state data; specifically, for example: when the query rate and/or delay rate are large, it means that the request traffic is large or If it is in a saturated state, it is necessary to expand the capacity of the platform in the resource service application. Otherwise, it means that the thread group is idle and can be scaled down, that is, released.
- this embodiment may also include: displaying the load status information of the thread group, the resource service request quantity information corresponding to the current resource service application identifier, the thread group information corresponding to the current resource service application identifier, the At least one of the number of threads in the thread group, the amount of requests processed by the thread group, the idle state information of the thread group, the release information of the thread group, and the expansion information of the platform in the resource service application information.
- the above is a description of an embodiment of a scheduling method for an enterprise digital middle station resource service application provided by the present application.
- the difference between this embodiment of the scheduling method and the embodiment of the scheduling system is that the embodiment of the scheduling method is implemented by the scheduling system
- the perspective of the local monitoring platform of the example is described as a starting point. Therefore, the specific content of the scheduling method embodiment can refer to the content of the local monitoring platform in the above scheduling system embodiment, and will not be repeated here.
- FIG. 3 for an embodiment of a scheduling device for an enterprise digital middle platform resource service application. Since the device embodiment is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.
- the device embodiments described below are illustrative only.
- Figure 3 is a schematic structural diagram of an embodiment of an enterprise digital middle platform resource service application scheduling device from the perspective of a local monitoring platform; the scheduling device embodiment includes:
- the first obtaining unit 301 is configured to create a thread group corresponding to the resource service application identifier located in the resource service application platform according to the obtained resource service application identifier; wherein, the resource service application identifier is used in the resource service application In the scenario, describe the participating identity information of the resource service application.
- the first acquisition unit 301 may include: a list acquisition subunit and a creation subunit; the list acquisition subunit is configured to acquire a resource service application for storing the resource service application in response to a startup event of the platform in the resource service application. An identified resource service application identification list; the creation subunit is configured to create the thread group corresponding to the resource service application identification according to the resource service application identification list.
- the second acquiring unit 302 is configured to acquire a resource service request from a platform in 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 one or more of the same resource service application identifiers. Resource service request.
- it may further include: a data acquisition unit and a processing unit, the data acquisition unit is used to acquire the execution state data of the resource service request executed by the thread group; Expand or shrink the thread group based on the execution state data.
- it may further include: a sending unit, configured to send the execution state data to the resource service application identification list.
- it may further include: a display unit, configured to display the load status information of the thread group on the interface, the resource service request quantity information corresponding to the current resource service application identifier, and the resource service request quantity information corresponding to the current resource service application identifier.
- Thread group information, thread number information of the thread group, request volume information processed by the thread group, idle state information of the thread group, release information of the thread group, and platform expansion of the resource service application at least one of the information.
- this application also provides a scheduling method for Taichung resource service application in enterprise digital center, as shown in Figure 4, which is a global monitoring method in the scheduling method for Taichung resource service application in enterprise digital center provided by this application
- the flow chart of the embodiment from the perspective of the platform, the embodiment of the scheduling method is mainly described from the perspective of the global monitoring platform in the embodiment of the scheduling system, which may specifically include:
- Step S401 Obtain the resource service request execution status data of the resource service application identifier in the resource service application identifier list; wherein the resource service application identifier is used to describe the participation identity information of the resource service application in the resource service application scenario.
- the resource service request execution status data in the step S401 can be uploaded to the resource service application identification database through the local monitoring platform, and can include: request traffic processing data corresponding to the resource service application identity information, for example: query rate per second (QPS , Queries-per-second), delay rate, throughput, etc.
- request traffic processing data corresponding to the resource service application identity information, for example: query rate per second (QPS , Queries-per-second), delay rate, throughput, etc.
- Step S402 According to the execution status of the resource service request, expand or shrink the capacity of the resource service application platform; wherein, the resource service application platform includes the resource service application platform created according to the obtained resource service application identifier and located in the resource service application platform , the thread group corresponding to the resource service application identifier.
- the resource service application platform includes the resource service application platform created according to the obtained resource service application identifier and located in the resource service application platform , the thread group corresponding to the resource service application identifier.
- the resource service application platform includes the resource service application platform created according to the obtained resource service application identifier and located in the resource service application platform , the thread group corresponding to the resource service application identifier.
- FIG. 5 is a schematic structural diagram of an embodiment from the perspective of the global monitoring platform in a scheduling device for resource service applications in an enterprise digital platform provided by the present application.
- the embodiment of the scheduling device includes:
- the acquiring unit 501 is configured to acquire the resource service request execution status of the resource service application identifier in the resource service application identifier list; wherein, the resource service application identifier is used to describe the participation identity of the resource service application in the resource service application scenario information;
- the processing unit 502 is configured to expand or shrink the resource service application platform according to the execution status of the resource service request; wherein, the resource service application platform includes a resource service application located in the resource service application created according to the obtained resource service application identifier. In the middle platform, the thread group corresponding to the resource service application identifier.
- this application also provides a scheduling method for Taichung resource service application in enterprise digital center, as shown in Fig.
- the flow chart of the embodiment of the perspective of the global monitoring platform, the embodiment of the scheduling method is described from multiple angles, that is, it includes first-level scheduling and second-level scheduling, and the first-level scheduling corresponds to the local monitoring platform in the scheduling system embodiment , the secondary scheduling corresponds to the global monitoring platform in the scheduling system.
- the specific implementation process of this scheduling method embodiment may include:
- Step S601 The local monitoring platform creates a thread group corresponding to the resource service application identifier located in the resource service application platform according to the obtained resource service application identifier; wherein, the resource service application identifier is used in the resource service application scenario , describing the participating identity information of the resource service application;
- Step S602 The local monitoring platform obtains the resource service request from the resource service application platform; wherein, the local monitoring platform corresponds to the resource service application platform;
- Step S603 The local monitoring platform routes the resource service request to the thread group matching the resource service application identifier; wherein, the thread group executes one or more resource service application identifiers of the same The resource service request;
- Step S604 The global monitoring platform responds to the resource service request execution status sent by the local monitoring platform to the resource service application identifier in the resource service application identifier list, and expands or shrinks the resource service application platform Allow.
- step S601 to step S604 For the specific content of the above step S601 to step S604, reference may be made to the content of the above scheduling system embodiment, and the corresponding or identical content will not be repeated here.
- this application also provides a scheduling device for resource service applications in enterprise digital platforms, as shown in FIG.
- the creation unit 701 is used for the local monitoring platform to create a thread group corresponding to the resource service application identification in the resource service application platform according to the obtained resource service application identification; wherein, the resource service application identification is used in the resource service In the application scenario, describe the participating identity information of the resource service application;
- the obtaining unit 702 is used for the local monitoring platform to obtain the resource service request of the resource service application platform; wherein, the local monitoring platform corresponds to the resource service application platform;
- the routing unit 703 is used for the local monitoring platform to route the resource service request to the thread group matching the resource service application identifier; wherein, the thread group executes one or more same resource services The resource service request identified by the application;
- the processing unit 704 is used for the global monitoring platform to respond to the resource service request execution status sent by the local monitoring platform to the resource service application identification in the resource service application identification list, and perform the resource service application middle platform Expand or shrink.
- the present application also provides a computer storage medium for storing data generated by the network platform, and a program for processing the data generated by the network platform;
- step S201 When the program is read and executed by the processor, it executes the content from step S201 to step S203 in the embodiment of the scheduling method of resource service application in the enterprise digital center as described above; or executes the resource service application in the enterprise digital center as described above
- step S401 to step S402 in the embodiment of the scheduling method; or, execute the contents of step S601 to step S604 in the embodiment of the scheduling method of resource service application in the platform of the enterprise digital center as described above.
- the present application also provides an electronic device, as shown in FIG. 8 , the embodiment of the electronic device includes:
- the memory 802 is used to store a program for processing data generated by the network platform.
- the program When the program is read and executed by the processor, it executes steps S201 to The content of step S203; or, execute the contents of step S401 to step S402 in the embodiment of the scheduling method of resource service application in the enterprise digital center as described above; or, execute the embodiment of the scheduling method of resource service application in the enterprise digital center as described above Contents in steps S601 to S604.
- a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
- processors CPUs
- input/output interfaces network interfaces
- memory volatile and non-volatile memory
- Memory may include non-permanent storage in computer readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM. Memory is an example of computer readable media.
- RAM random access memory
- ROM read-only memory
- flash RAM flash random access memory
- Computer-readable media include permanent and non-permanent, removable and non-removable media.
- Information storage can be realized by any method or technology.
- 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 Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
- computer-readable media excludes non-transitory computer-readable media, such as modulated data signals and carrier waves.
- the embodiments of the present application may be provided as methods, systems or computer program products. Accordingly, the present application can 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, etc.) having computer-usable program code embodied therein.
- a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
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
本申请公开一种企业数字中台中资源服务应用的调度系统和方法，所述系统包括：位于所述企业数字中台中的资源服务应用标识配置库、资源服务应用中台、以及与所述资源服务应用中台对应的本地监控平台；所述资源服务应用标识配置库用于存储资源服务应用标识的资源服务应用标识列表；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；所述本地监控平台获取所述资源服务应用中台的多个资源服务请求，并将所述多个资源服务请求分别路由到，根据所述资源服务应用标识列表创建的与所述资源服务应用标识对应的线程组中。从而实现不同资源服务应用的资源服务请求流量的南北隔离。
Description
本申请要求于2022年01月05日提交中国专利局、申请号为202210006017.2、申请名称为“一种企业数字中台中资源服务应用的调度系统和方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请涉及计算机技术领域，具体涉及一种企业数字中台中资源服务应用的调度系统和方法。本申请同时涉及一种计算机存储介质和电子设备。
随着科学技术的不断发展，信息化、智能化等计算机基础被广泛的应用到各个行业领域，以及日常生活中。而在产业和技术的驱动下，数字化转型已经成为企业的共识。数字化转型(Digital transformation)是建立在数字化转换(Digitization)、数字化升级(Digitalization)基础上，能够触及企业核心业务，建立以商业运营模式为目标的转型。
随着企业共享能力以数字化服务的方式不断推进和深化，为将企业的核心能力随着业务不断发展以数字化形式沉淀到平台，形成以服务为中心，由业务中台和数据中台构建数据闭环运转的运营体系的数字中台成为企业进行数字化转型的有效系统形态和组织方法，以供企业更高效的进行业务探索和创新，实现以数字化资产的形态构建企业核心差异化竞争力。
发明内容
本申请提供一种企业数字中台中资源服务应用的调度系统和方法，以解决现有技术中由于中台内请求流量隔离方式不灵活以及资源浪费问题。
本申请提供一种企业数字中台中资源服务应用的调度系统，包括：位于所述企业数字中台中的资源服务应用标识配置库、资源服务应用中台、以及与所述资源服务应用中台对应的本地监控平台；
所述资源服务应用标识配置库用于存储资源服务应用标识的资源服务应用标识列表；其中，所述资源服务应用标识用于在资源服务应用场景中，描 述资源服务应用的参与身份信息；
所述本地监控平台获取所述资源服务应用中台的多个资源服务请求，并将所述多个资源服务请求分别路由到，根据所述资源服务应用标识列表创建的与所述资源服务应用标识对应的线程组中。
在一些实施例中，所述本地监控平台获取所述资源服务应用标识配置库中的所述资源服务应用标识列表，根据所述资源服务应用标识列表中所述资源服务应用标识创建与所述资源服务应用标识对应的所述线程组。
在一些实施例中，所述本地监控平台获取所述线程组执行所述资源服务请求的执行状态数据；根据所述执行状态数据对所述线程组进行扩容或缩容。
在一些实施例中，所述资源服务应用标识配置库还存储所述线程组执行所述资源服务请求的执行状态数据。
在一些实施例中，还包括：全局监控平台，用于获取所述资源服务应用标识配置库中与所述资源服务应用标识匹配的所述资源服务请求的执行状态数据；根据所述执行状态数据，确定对所述多个资源服务应用中台进行扩容或缩容。
在一些实施例中，还包括：
显示设备，用于在界面展示所述线程组的负载状态信息、与当前资源服务应用标识对应的资源服务请求数量信息、与当前资源服务应用标识对应所述线程组信息、所述线程组的线程数量信息、所述线程组处理的请求量信息、所述线程组的空闲状态信息、所述线程组的释放信息，以及所述资源服务应用中台的扩容信息中的至少一种信息。
本申请还提供一种企业数字中台中资源服务应用的调度方法，包括：
根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；
获取资源服务应用中台的多个资源服务请求；
将所述多个资源服务请求分别路由到，与所述资源服务应用标识相匹配的所述线程组中。
在一些实施例中，所述根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务标识对应的线程组，包括：
响应于所述资源服务应用中台的启动事件，获取用于存储所述资源服务 应用标识的资源服务应用标识列表；
根据所述资源服务应用标识列表，创建与所述资源服务应用标识对应的所述线程组。
在一些实施例中，还包括：
获取所述线程组执行所述资源服务请求的执行状态数据；
根据所述执行状态数据对所述线程组进行扩容或缩容。
在一些实施例中，还包括：
将所述执行状态数据发送到所述资源服务应用标识列表。
本申请还提供一种企业数字中台中资源服务应用的调度方法，包括：
获取资源服务应用标识列表中所述资源服务应用标识的资源服务请求执行状态；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；
根据所述资源服务请求执行状态，对所述资源服务应用中台进行扩容或缩容；其中，所述资源服务应用中台中包括根据获取的资源服务应用标识创建的位于资源服务应用中台内，与所述资源服务应用标识对应的线程组。
本申请还提供一种企业数字中台中资源服务应用的调度方法，包括：
本地监控平台根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；
所述本地监控平台获取资源服务应用中台的多个资源服务请求；其中，所述本地监控平台与所述资源服务应用中台对应；
所述本地监控平台将所述多个资源服务请求分别路由到，与所述资源服务应用标识相匹配的所述线程组中；
全局监控平台响应于所述本地监控平台发送到，所述资源服务应用标识列表中的所述资源服务应用标识的资源服务请求执行状态，对所述资源服务应用中台进行扩容或缩容。
本申请还提供一种计算机存储介质，用于存储网络平台产生数据，以及对应所述网络平台产生数据进行处理的程序；
所述程序在被处理器读取执行时，执行如上所述的企业数字中台中资源服务应用的调度方法；或者，执行如上所述的企业数字中台中资源服务应用的调度方法；或者，执行如上所述的企业数字中台中资源服务应用的调度方 法。
本申请还提供一种电子设备，包括：
处理器；
存储器，用于存储对网络平台产生数据进行处理的程序，所述程序在被所述处理器读取执行时，执行如上所述的企业数字中台中资源服务应用的调度方法；或者，执行如上所述的企业数字中台中资源服务应用的调度方法；或者，执行如上所述的企业数字中台中资源服务应用的调度方法。
与现有技术相比，本申请具有以下优点：
本申请提供的一种企业数字中台中资源服务应用的调度系统和方法一方面能够通过本地监控平台将获取的资源服务请求路由到，根据所述资源服务应用标识列表创建的与所述资源服务应用标识对应的线程组中，从而使得资源服务请求均可以在对应的线程组中进行处理，实现不同资源服务应用的资源服务请求流量的南北隔离；另一方面能够根据全局监控平台获取的资源服务应用标识配置库中与所述资源服务应用标识匹配的所述资源服务请求的执行状态数据，实现对资源服务应用中台的扩容或缩容，从而避免资源浪费，实现资源服务请求的精确调度和调整。
图1是本申请提供的一种企业数字中台中资源服务应用的调度系统实施例的结构示意图；
图2是本申请提供的一种企业数字中台中资源服务应用的调度方法中以本地监控平台为角度的实施例的流程图；
图3是本申请提供的一种企业数字中台中资源服务应用的调度装置中以本地监控平台为角度的实施例的结构示意图；
图4是本申请提供的一种企业数字中台中资源服务应用的调度方法中以全局监控平台为角度的实施例的流程图；
图5是本申请提供的一种企业数字中台中资源服务应用的调度装置中以全局监控平台为角度的实施例的结构示意图；
图6是本申请提供的一种企业数字中台中资源服务应用的调度方法中以本地和全局监控平台为角度的实施例的流程图；
图7是本申请提供的一种企业数字中台中资源服务应用的调度装置中以 本地和全局监控平台为角度的实施例的结构示意图；
图8是本申请提供的一种电子设备实施例的结构示意图。
在下面的描述中阐述了很多具体细节以便于充分理解本申请。但是本申请能够以很多不同于在此描述的其它方式来实施，本领域技术人员可以在不违背本申请内涵的情况下做类似推广，因此本申请不受下面公开的具体实施的限制。
本申请中使用的术语是仅仅出于对特定实施例描述的目的，而非旨在限制本申请。在本申请中和所附权利要求书中所使用的描述方式例如：“一种”、“第一”、和“第二”等，并非对数量上的限定或先后顺序上的限定，而是用来将同一类型的信息彼此区分。
结合上述背景技术可知，企业数字中台是面向业务的能力组合、共享和复用，提供集成化的解决方案，目的在于提高研发效率，降低创新成本。所述企业数字中台可以包括用户、组合、平台、数据、标准、规范，是用户和系统的整体体系。即：企业数字中台是将企业的共性需求进行抽象，并打造成平台化、组件化的系统能力，以接口、组件等形式共享给各业务单元使用的企业级能力复用平台。
企业数字中台会以共享的方式为各个应用提供服务，故而应用服务成为企业数字中台中关键实体之一。在共享方式的背景下，各个应用服务之间互不影响则是企业数字中台正常运行的重要因素之一，而现有对企业数字中台中各个应用服务之间的流量隔离通常是采用物理隔离方式，即为不同的应用服务部署不同的中台应用实例，从而实现企业数字中台中南北方向上应用服务流量的隔离，然而，该种物理隔离方式存在问题如下：
1、通过人工方式部署多份中台应用示例，不灵活；
2、为应用服务单独部署中台应用示例，无法根据实际流量状态进行资源调派，导致资源浪费。
鉴于此，本申请构思提供一种企业数字中台中资源服务应用的调度系统和方式，能够解决人工部署中台应用实例不灵活以及资源浪费的问题，下面将对本申请提供的企业数字中台中资源服务应用的调度系统和方法进行详细说明。
如图1所示，图1是本申请提供的一种企业数字中台中资源服务应用的调度系统实施例的结构示意图；该调度系统实施例包括：资源服务应用标识配置库101，企业数字中台中的资源服务应用中台102，以及与所述资源服务应用中台对应的本地监控平台(Local Monitor)103；
所述资源服务应用标识配置库101用于存储资源服务应用标识的资源服务应用标识列表；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息。也可以称之为业务身份，可以是指在应用场景中应用服务的参与身份，是资源服务应用中台执行工作能力的独立业务单元。用于能力接入的调用鉴权以及扩展点实现的路由策略。所述业务身份可以是即资源服务应用的级别，针对同一用户可能存在多个资源服务应用，不同资源服务应用具有不同身份级别，也可能属于同一身份级别。资源服务应用的身份级别下还可以包括子身份级别，即能够区分资源服务应用的整体链路的身份级别。例如：应用1为一级业务身份，应用2也是一级业务身份，应用3从属于应用1是二级业务身份。
在本实施例中，所述资源服务应用可以是各类应用服务，例如：生活、购物、医药等等应用服务。资源服务可以是例如：商品信息查询、商品状态管理、订单查询服务等功能服务。所述资源服务应用标识列表也可以称为资源服务身份配置列表，存储资源服务应用身份信息的列表。所述资源服务身份配置列表还可以存储，所述本地监控平台103传输的，与资源服务应用身份信息对应的流量处理数据，例如：每秒查询率(QPS，Queries-per-second)、延时率、吞吐量等。
所述本地监控平台103获取所述资源服务应用中台102的资源服务请求，并将所述资源服务请求路由到，根据所述资源服务应用标识列表创建的与所述资源服务应用标识对应的线程组中；其中，所述线程组执行一个或多个同一资源服务应用标识的所述资源服务请求。
本实施例中，所述资源服务应用中台102可以通过企业数字中台进行建设。所述本地监控平台103获取所述资源服务应用标识配置库101中的所述资源服务应用标识列表，根据所述资源服务应用标识列表中所述资源服务应用标识创建与所述资源服务应用标识对应的所述线程组(group)，例如线程组group1和线程组group2。
所述本地监控平台103在所述资源服务应用中台102启动时，读取所述 资源服务应用标识配置库101中的资源服务应用标识列表。所述本地监控平台103根据读取的所述资源服务应用标识列表创建所述线程组。终端设备发起的资源服务请求会被传输到所述资源服务应用中台102，所述资源服务应用中台102会根据资源服务应用标识将资源服务请求分别路由到线程组。例如：所述资源服务应用标识配置库101中存储有资源服务应用1、资源服务应用2、资源服务应用3、资源服务应用4的资源服务应用标识。所述资源服务请求可以是针对资源服务应用1、资源服务应用2、资源服务应用3中的一个或多个应用的请求，针对每一个资源服务应用的资源服务请求可以是一个或多个请求内容，例如访问请求、订单请求、支付请求等。当资源服务应用中台启动时，本地监控平台会读取资源服务应用标识配置库中标识，然后为资源服务应用标识创建对应的线程组，即线程组1对应于资源服务应用1的资源服务请求、线程组2对应于资源服务应用2的资源服务请求、线程组3资源服务应用3的资源服务请求和线程组4对应与资源服务应用4的资源服务请求。线程组1、线程组2、线程组3和线程组4可以构成线程组集合。向所述资源服务应用1、资源服务应用2、资源服务应用3、资源服务应用4等发起的资源服务请求会先传输到本地监控平台103，所述本地监控平台103根据资源服务应用标识将资源服务请求1路由到线程组1，请求2理由到线程组2，请求3路由到线程组3，请求4路由到线程组4，从而使得请求1到请求4之间相互独立，实现流量隔离。当然，根据实际请求流量的状态，也可以将不同资源服务应用标识的资源服务请求路由到同一个线程组中，从而减少资源浪费，因为，在请求流量较小的情况下，资源服务应用之间的影响可以忽略不计，或者产生的影响不会涉及各资源服务应用之间的运行状态。
本实施例中，为避免资源浪费，可以通过所述本地监控平台103获取所述线程组执行所述资源服务请求的执行状态数据，根据所述执行状态数据对所述线程组进行扩容或缩容。所述执行状态数据可以包括：与资源服务应用身份信息对应的请求流量处理数据，例如：每秒查询率(QPS，Queries-per-second)、延时率、吞吐量等。当查询率和/或延时率较大时，说明请求流量较大或者处于饱和状态，需要对线程组进行扩容，反之缩容。当吞吐量较大，说明请求流程较小可以对线程组进行缩容，反之扩容。
本实施例中，对于所述资源服务应用中台也可以根据请求流量状态进行缩容或扩容，即增加资源服务应用中台实例或者减小资源服务应用中台实例。 具体地，可以包括：
全局监控平台(GloablMonitor)104，用于获取所述资源服务应用标识配置库中与所述资源服务应用标识匹配的所述资源服务请求的执行状态数据；根据所述执行状态数据，确定对所述资源服务应用中台进行扩容或缩容。具体地，所述全局监控平台104通过资源服务应用标识配置库中的资源服务应用标识，获取与所述资源服务应用标识对应的资源服务应用的请求执行状态(也可以理解为负载状态)，当请求执行数量大于或等于设置的扩容阈值，则为请求服务的资源服务应用构建新的资源服务应用中台，并创建线程组，此时创建的线程组可以是针对请求执行数量大于或等于与设置的扩容阈值，所对应的资源服务应用标识，可以将负载超出扩容阈值的资源服务应用标识对应的资源服务请求路由到新的资源服务应用中台的线程组中。如果请求执行数量大于或等于设置的缩容阈值，说明资源服务应用中台中存在空闲的线程组，则将空闲的线程组进行释放，从而实现线程组的缩容。
以上是对本申请提供的一种企业数字中台资源服务应用的调度系统实施例的描述，该调度系统实施例一方面能够通过本地监控平台将获取的资源服务请求路由到，根据所述资源服务应用标识列表创建的与所述资源服务应用标识对应的线程组中，从而使得资源服务请求均可以在对应的线程组中进行处理，实现不同资源服务应用的资源服务请求流量的隔离；另一方面能够根据全局监控平台获取的资源服务应用标识配置库中与所述资源服务应用标识匹配的所述资源服务请求的执行状态数据，实现对资源服务应用中台的扩容或对资源服务应用中台的线程组进行缩容，从而避免资源浪费，实现资源服务请求的精确调度和调整。
为便于了解资源服务请求的调度情况，本实施例还包括：显示设备，用于在界面展示所述线程组的负载状态信息、与当前资源服务应用标识对应的资源服务请求数量信息、与当前资源服务应用标识对应所述线程组信息、所述线程组的线程数量信息、所述线程组处理的请求量信息、所述线程组的空闲状态信息、所述线程组的释放信息，以及所述资源服务应用中台的扩容信息中的至少一种信息。
基于上述内容，本申请还提供一种企业数字中台中资源服务应用的调度方法，如图2所示，图2是本申请提供的一种企业数字中台资源服务应用的调度方法中以本地监控平台为角度的实施例的流程图，该调度方法实施例主 要是以调度系统实施例中的本地监控平台为角度进行描述，具体可以包括：
步骤S201：根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息。
在本实施例中，所述步骤S201中的所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息。所述资源服务应用可以是各类应用服务，例如：生活、购物、医药等等应用服务。资源服务可以是例如：商品信息查询、商品状态管理、订单查询服务等功能服务。资源服务应用标识可以理解为是表征资源服务应用的标识信息也可以称为身份信息，所述身份信息可以指在应用场景中应用服务的参与身份，是资源服务应用中台执行工作能力的独立业务单元。用于能力接入的调用鉴权以及扩展点实现的路由策略。所述资源服务应用标识列表也可以称为资源服务身份配置列表，存储资源服务应用身份信息的列表。
本实施例中，所述资源服务应用中台可以通过企业数字中台进行建设。所述线程组可以包括至少两个线程组group1和group2。创建线程组时，可以是每个资源服务应用标识对应一个线程组，也可以是多个资源服务应用标识对应一个线程组。
本实施例中，所述步骤S201的具体实现过程可以包括：
步骤S201-1：响应于所述资源服务应用中台的启动事件，获取用于存储所述资源服务应用标识的资源服务应用标识列表；所述启动事件可以是对资源服务应用中台的触发。
步骤S201-2：根据所述资源服务应用标识列表，创建与所述资源服务应用标识对应的所述线程组；所述创建的方式可以是同一个资源服务应用标识对应一个线程组，和/或，多个不同资源服务应用标识对应一个线程组。即，创建与资源服务应用标识对应的所述线程组，能够在后续资源服务请求调度时，将与资源服务应用标识对应的资源服务请求调度到相应的线程组中进行执行，从而实现资源服务应用中台对资源服务请求的隔离。
步骤S202：获取资源服务应用中台的资源服务请求。
本实施例中，所述步骤S202的具体实现过程可以是，终端设备发起的资源服务请求会被传输到所述资源服务应用中台，所述资源服务请求可以是针对资源服务应用1、资源服务应用2、资源服务应用3中的一个或多个应用的 请求，针对每一个资源服务应用的资源服务请求可以是一个或多个请求内容，例如访问请求、订单请求、支付请求等。
步骤S203：将所述资源服务请求路由到，与所述资源服务应用标识相匹配的所述线程组中；其中，所述线程组可以执行一个或多个同一资源服务应用标识的所述资源服务请求。
所述步骤S203可以理解为，当资源服务应用中台启动时，读取资源服务应用标识，然后为资源服务应用标识创建对应的线程组，即线程组1对应于资源服务应用1、线程组2对应于资源服务应用2、线程组3资源服务应用3和线程组4资源服务应用4。线程组1、线程组2、线程组3和线程组4构成线程组集合。获取所述资源服务应用1、资源服务应用2、资源服务应用3、资源服务应用4等发起的资源服务请求，根据资源服务应用标识将资源请求中的请求1路由到线程组1，请求2理由到线程组2，请求3路由到线程组3，请求4路由到线程组4，从而使得请求1到请求4之间均是在各自匹配的线程组中进行执行，因此相互独立，实现流量隔离。当然，根据实际请求流量的状态，也可以将不同资源服务应用标识的资源服务请求路由到同一个线程组中，因为，在请求流量较小的情况下，资源服务应用之间的影响可以忽略不计，或者产生的影响不会涉及各资源服务应用之间的运行状态，并且还能够减少资源的浪费。
基于上述，为避免资源浪费。本实施例还可以包括：
获取所述线程组执行所述资源服务请求的执行状态数据；所述执行状态数据可以包括：与资源服务应用身份信息对应的请求流量处理数据，例如：每秒查询率(QPS，Queries-per-second)、延时率、吞吐量等。
根据所述执行状态数据对所述资源服务应用中台进行扩容或者对所述线程组进行缩容；具体地，例如：当查询率和/或延时率较大时，说明请求流量较大或者处于饱和状态，需要对资源服务应用中台进行扩容，反之则说明所述线程组空闲，可以进行缩容，即释放。
相应地，本实施例中还可以包括：展示所述线程组的负载状态信息、与当前资源服务应用标识对应的资源服务请求数量信息、与当前资源服务应用标识对应所述线程组信息、所述线程组的线程数量信息、所述线程组处理的请求量信息、所述线程组的空闲状态信息、所述线程组的释放信息，以及所述资源服务应用中台的扩容信息中的至少一种信息。
以上是对本申请提供的一种企业数字中台资源服务应用的调度方法实施例的描述，该调度方法实施例与所述调度系统实施例的区别在于，该调度方法实施例以所述调度系统实施例的本地监控平台角度为出发点进行描述，因此，关于该调度方法实施例的具体内容可以参考上述调度系统实施例中关于本地监控平台的内容，此处不再重复赘述。
以上是对本申请提供的一种企业数字中台资源服务应用的调度方法实施例的具体描述，与前述提供的一种企业数字中台资源服务应用的调度方法实施例相对应，本申请还公开一种企业数字中台资源服务应用的调度装置实施例，请参看图3，由于装置实施例基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。下述描述的装置实施例仅仅是示意性的。
如图3所示，图3是本申请提供的一种企业数字中台资源服务应用的调度装置中以本地监控平台为角度的实施例的结构示意图；该调度装置实施例包括：
第一获取单元301，用于根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息。
所述第一获取单元301可以包括：列表获取子单元和创建子单元；所述列表获取子单元，用于响应于所述资源服务应用中台的启动事件，获取用于存储所述资源服务应用标识的资源服务应用标识列表；所述创建子单元，用于根据所述资源服务应用标识列表，创建与所述资源服务应用标识对应的所述线程组。
第二获取单元302，用于获取资源服务应用中台的资源服务请求；
路由单元303，用于将所述资源服务请求路由到，与所述资源服务应用标识相匹配的所述线程组中；其中，所述线程组执行一个或多个同一资源服务应用标识的所述资源服务请求。
在一些实施例中，还可以包括：数据获取单元和处理单元，所述数据获取单元，用于获取所述线程组执行所述资源服务请求的执行状态数据；所述处理单元，用于根据所述执行状态数据对所述线程组进行扩容或缩容的处理。
在一些实施例中，还可以包括：发送单元，用于将所述执行状态数据发送到所述资源服务应用标识列表。
在一些实施例中，还可以包括：展示单元，用于在界面展示所述线程组的负载状态信息、与当前资源服务应用标识对应的资源服务请求数量信息、与当前资源服务应用标识对应所述线程组信息、所述线程组的线程数量信息、所述线程组处理的请求量信息、所述线程组的空闲状态信息、所述线程组的释放信息，以及所述资源服务应用中台的扩容信息中的至少一种信息。
以上是对本申请提供的一种企业数字中台中资源服务应用的调度装置实施例的描述，该调度装置实施例的内容可以参考上述企业数字中台中资源服务应用的调度系统实施例和调度方法实施例的相关内容，此处不再重复赘述。
基于上述内容，本申请还提供一种企业数字中台中资源服务应用的调度方法，如图4所示，图4是本申请提供的一种企业数字中台中资源服务应用的调度方法中以全局监控平台为角度的实施例的流程图，该调度方法实施例主要是以调度系统实施例中的全局监控平台为角度进行描述，具体可以包括：
步骤S401：获取资源服务应用标识列表中所述资源服务应用标识的资源服务请求执行状态数据；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息。
所述步骤S401中的资源服务请求执行状态数据可以通过本地监控平台上传到资源服务应用标识库中，可以包括：与资源服务应用身份信息对应的请求流量处理数据，例如：每秒查询率(QPS，Queries-per-second)、延时率、吞吐量等。具体可以参考上述调度系统实施例中的描述。
步骤S402：根据所述资源服务请求执行状态，对资源服务应用中台进行扩容或缩容；其中，所述资源服务应用中台中包括根据获取的资源服务应用标识创建的位于资源服务应用中台内，与所述资源服务应用标识对应的线程组。例如：当请求执行数量大于或等于设置的扩容阈值，则为请求服务的资源服务应用构建新的资源服务应用中台。当请求执行数量大于或等于设置的缩容阈值，则将请求服务对应的资源服务应用中台中的所有请求合并到其他资源服务应用中台并释放，从而实现资源服务应用中台的缩容。具体可以参考上述调度系统实施例中的描述。
以上是对本申请提供的一种企业数字中台中资源服务应用的调度方法实施例的描述，与前述提供的一种企业数字中台资源服务应用的调度方法实施例相对应，本申请还公开一种企业数字中台资源服务应用的调度装置实施例，请参看图5，由于装置实施例基本相似于方法实施例，所以描述得比较简单， 相关之处参见方法实施例的部分说明即可。下述描述的装置实施例仅仅是示意性的。
如图5所示，图5是本申请提供的一种企业数字中台中资源服务应用的调度装置中以全局监控平台为角度的实施例的结构示意图，所述调度装置实施例包括：
获取单元501，用于获取资源服务应用标识列表中所述资源服务应用标识的资源服务请求执行状态；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；
处理单元502，用于根据所述资源服务请求执行状态，对资源服务应用中台进行扩容或缩容；其中，所述资源服务应用中台中包括根据获取的资源服务应用标识创建的位于资源服务应用中台内，与所述资源服务应用标识对应的线程组。
关于所述获取单元501和处理单元502的具体实现过程可以参考上述调度系统实施例的内容以及步骤S401到步骤S402的内容，此处不再重复赘述。
基于上述内容，本申请还提供一种企业数字中台中资源服务应用的调度方法，如图6所示，图6是本申请提供的一种企业数字中台中资源服务应用的调度方法中以本地和全局监控平台为角度的实施例的流程图，该调度方法实施例是以多角度描述，即：包括一级调度和二级调度，所述一级调度对应于调度系统实施例中的本地监控平台，所述二级调度对应于调度系统中的全局监控平台。该调度方法实施例的具体实现过程可以包括：
步骤S601：本地监控平台根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；
步骤S602：所述本地监控平台获取资源服务应用中台的资源服务请求；其中，所述本地监控平台与所述资源服务应用中台对应；
步骤S603：所述本地监控平台将所述资源服务请求路由到，与所述资源服务应用标识相匹配的所述线程组中；其中，所述线程组执行一个或多个同一资源服务应用标识的所述资源服务请求；
步骤S604：全局监控平台响应于所述本地监控平台发送到，所述资源服务应用标识列表中的所述资源服务应用标识的资源服务请求执行状态，对所述资源服务应用中台进行扩容或缩容。
关于上述步骤S601到步骤S604的具体内容可以参考上述调度系统实施例的内容，此处不再对相应或相同内容进行重复描述。
基于上述，本申请还提供一种企业数字中台中资源服务应用的调度装置，如图7所示，图7是本申请提供的一种企业数字中台中资源服务应用的调度装置中以本地和全局监控平台为角度的实施例的结构示意图，该调度装置实施例包括：
创建单元701，用于本地监控平台根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；
获取单元702，用于所述本地监控平台获取资源服务应用中台的资源服务请求；其中，所述本地监控平台与所述资源服务应用中台对应；
路由单元703，用于所述本地监控平台将所述资源服务请求路由到，与所述资源服务应用标识相匹配的所述线程组中；其中，所述线程组执行一个或多个同一资源服务应用标识的所述资源服务请求；
处理单元704，用于全局监控平台响应于所述本地监控平台发送到，所述资源服务应用标识列表中的所述资源服务应用标识的资源服务请求执行状态，对所述资源服务应用中台进行扩容或缩容。
基于上述内容，本申请还提供一种计算机存储介质，用于存储网络平台产生数据，以及对应所述网络平台产生数据进行处理的程序；
所述程序在被处理器读取执行时，执行如上所述企业数字中台中资源服务应用的调度方法实施例中步骤S201到步骤S203的内容；或者，执行如上所述企业数字中台中资源服务应用的调度方法实施例中步骤S401到步骤S402的内容；或者，执行如上所述企业数字中台中资源服务应用的调度方法实施例中步骤S601到步骤S604的内容。
基于上述内容，本申请还提供一种电子设备，如图8所示，该电子设备实施例包括：
处理器801；
存储器802，用于存储对网络平台产生数据进行处理的程序，所述程序在被所述处理器读取执行时，执行如上所述企业数字中台中资源服务应用的调度方法实施例中步骤S201到步骤S203的内容；或者，执行如上所述企业数 字中台中资源服务应用的调度方法实施例中步骤S401到步骤S402的内容；或者，执行如上所述企业数字中台中资源服务应用的调度方法实施例中步骤S601到步骤S604的内容。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
1、计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括非暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
2、本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请虽然以较佳实施例公开如上，但其并不是用来限定本申请，任何本领域技术人员在不脱离本申请的精神和范围内，都可以做出可能的变动和修改，因此本申请的保护范围应当以本申请权利要求所界定的范围为准。
Claims (14)
- 一种企业数字中台中资源服务应用的调度系统，其特征在于，包括：位于所述企业数字中台中的资源服务应用标识配置库、资源服务应用中台、以及与所述资源服务应用中台对应的本地监控平台；所述资源服务应用标识配置库用于存储资源服务应用标识的资源服务应用标识列表；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；所述本地监控平台获取所述资源服务应用中台的多个资源服务请求，并将所述多个资源服务请求分别路由到，根据所述资源服务应用标识列表创建的与所述资源服务应用标识对应的线程组中。
- 根据权利要求1所述的企业数字中台中资源服务应用的调度系统，其特征在于，所述本地监控平台获取所述资源服务应用标识配置库中的所述资源服务应用标识列表，根据所述资源服务应用标识列表中所述资源服务应用标识创建与所述资源服务应用标识对应的所述线程组。
- 根据权利要求1所述的企业数字中台中资源服务应用的调度系统，其特征在于，所述本地监控平台获取所述线程组执行所述资源服务请求的执行状态数据；根据所述执行状态数据对所述线程组进行扩容或缩容。
- 根据权利要求3所述的企业数字中台中资源服务应用的调度系统，其特征在于，所述资源服务应用标识配置库还存储所述线程组执行所述资源服务请求的执行状态数据。
- 根据权利要求1所述的企业数字中台中资源服务应用的调度系统，其特征在于，还包括：全局监控平台，用于获取所述资源服务应用标识配置库中与所述资源服务应用标识匹配的所述资源服务请求的执行状态数据；根据所述执行状态数据，确定对所述多个资源服务应用中台进行扩容或缩容。
- 根据权利要求1所述的企业数字中台中资源服务应用的调度系统，其特征在于，还包括：显示设备，用于在界面展示所述线程组的负载状态信息、与当前资源服务应用标识对应的资源服务请求数量信息、与当前资源服务应用标识对应所述线程组信息、所述线程组的线程数量信息、所述线程组处理的请求量信息、所述线程组的空闲状态信息、所述线程组的释放信息，以及所述资源服务应 用中台的扩容信息中的至少一种信息。
- 一种企业数字中台中资源服务应用的调度方法，其特征在于，包括：根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；获取资源服务应用中台的多个资源服务请求；将所述多个资源服务请求分别路由到，与所述资源服务应用标识相匹配的所述线程组中。
- 根据权利要求7所述的企业数字中台中资源服务应用的调度方法，其特征在于，所述根据获取的资源服务应用标识创建位于资源服务应用中台内，与所述资源服务标识对应的线程组，包括：响应于所述资源服务应用中台的启动事件，获取用于存储所述资源服务应用标识的资源服务应用标识列表；根据所述资源服务应用标识列表，创建与所述资源服务应用标识对应的所述线程组。
- 根据权利要求7所述的企业数字中台中资源服务应用的调度方法，其特征在于，还包括：获取所述线程组执行所述资源服务请求的执行状态数据；根据所述执行状态数据对所述线程组进行扩容或缩容。
- 根据权利要求9所述的企业数字中台中资源服务应用的调度方法，其特征在于，还包括：将所述执行状态数据发送到所述资源服务应用标识列表。
- 一种企业数字中台中资源服务应用的调度方法，其特征在于，包括：获取资源服务应用标识列表中所述资源服务应用标识的资源服务请求执行状态；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；根据所述资源服务请求执行状态，对所述资源服务应用中台进行扩容或缩容；其中，所述资源服务应用中台中包括根据获取的资源服务应用标识创建的位于资源服务应用中台内，与所述资源服务应用标识对应的线程组。
- 一种企业数字中台中资源服务应用的调度方法，其特征在于，包括：本地监控平台根据获取的资源服务应用标识创建位于资源服务应用中台 内，与所述资源服务应用标识对应的线程组；其中，所述资源服务应用标识用于在资源服务应用场景中，描述资源服务应用的参与身份信息；所述本地监控平台获取资源服务应用中台的多个资源服务请求；其中，所述本地监控平台与所述资源服务应用中台对应；所述本地监控平台将所述多个资源服务请求分别路由到，与所述资源服务应用标识相匹配的所述线程组中；全局监控平台响应于所述本地监控平台发送到，所述资源服务应用标识列表中的所述资源服务应用标识的资源服务请求执行状态，对所述资源服务应用中台进行扩容或缩容。
- 一种计算机存储介质，用于存储网络平台产生数据，以及对应所述网络平台产生数据进行处理的程序；所述程序在被处理器读取执行时，执行如上述权利要求7-10任意一项所述的企业数字中台中资源服务应用的调度方法；或者，执行如上述权利要求11所述的企业数字中台中资源服务应用的调度方法；或者，执行如上述权利要求12所述的企业数字中台中资源服务应用的调度方法。
- 一种电子设备，包括：处理器；存储器，用于存储对网络平台产生数据进行处理的程序，所述程序在被所述处理器读取执行时，执行如上述权利要求7-10任意一项所述的企业数字中台中资源服务应用的调度方法；或者，执行如上述权利要求11所述的企业数字中台中资源服务应用的调度方法；或者，执行如上述权利要求12所述的企业数字中台中资源服务应用的调度方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210006017.2A CN114036031B (zh) | 2022-01-05 | 2022-01-05 | 一种企业数字中台中资源服务应用的调度系统和方法 |
| CN202210006017.2 | 2022-01-05 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023131058A1 true WO2023131058A1 (zh) | 2023-07-13 |
Family
ID=80147291
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/143628 WO2023131058A1 (zh) | 2022-01-05 | 2022-12-29 | 一种企业数字中台中资源服务应用的调度系统和方法 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114036031B (zh) |
| WO (1) | WO2023131058A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116700907A (zh) * | 2023-08-04 | 2023-09-05 | 北京国电通网络技术有限公司 | 服务调用需求文档存储方法、装置、电子设备和可读介质 |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114036031B (zh) * | 2022-01-05 | 2022-06-24 | 阿里云计算有限公司 | 一种企业数字中台中资源服务应用的调度系统和方法 |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102789394A (zh) * | 2011-05-19 | 2012-11-21 | 阿里巴巴集团控股有限公司 | 一种并行处理消息的方法、装置、节点及服务器集群 |
| US20130110588A1 (en) * | 2011-10-26 | 2013-05-02 | Iex Corporation | Application usage and process monitoring in an enterprise environment |
| CN110324403A (zh) * | 2019-05-23 | 2019-10-11 | 平安科技（深圳）有限公司 | 动态分库路由方法、装置、服务器及存储介质 |
| CN111343275A (zh) * | 2020-03-02 | 2020-06-26 | 北京奇艺世纪科技有限公司 | 资源调度方法和系统 |
| CN111736977A (zh) * | 2020-07-21 | 2020-10-02 | 成都新希望金融信息有限公司 | 一种多中台的中央调度方法及系统 |
| CN112559486A (zh) * | 2020-11-11 | 2021-03-26 | 国网江苏省电力有限公司信息通信分公司 | 一种数据中台统一任务调度管理系统 |
| CN113392158A (zh) * | 2021-06-11 | 2021-09-14 | 中国工商银行股份有限公司 | 业务数据处理方法、装置及数据中台 |
| CN114036031A (zh) * | 2022-01-05 | 2022-02-11 | 阿里云计算有限公司 | 一种企业数字中台中资源服务应用的调度系统和方法 |
Family Cites Families (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004081725A2 (en) * | 2003-03-11 | 2004-09-23 | Gtv Solutions, Inc. | Communications interchange system |
| ATE513389T1 (de) * | 2003-06-20 | 2011-07-15 | Zte Corp | Verfahren zur ethernet-netzwerk-dienst- sicherheits-isolation |
| US7953916B2 (en) * | 2009-04-08 | 2011-05-31 | Intel Corporation | Dynamic, local retriggered interrupt routing discovery method |
| CN109582472B (zh) * | 2018-10-19 | 2021-05-18 | 华为技术有限公司 | 一种微服务处理方法及设备 |
| US11003566B2 (en) * | 2018-12-31 | 2021-05-11 | Paypal, Inc. | Tracking data flow through data services using a processing request identifier in callstack data |
| CN111984709A (zh) * | 2019-05-23 | 2020-11-24 | 云南青年学园科技有限公司 | 可视化大数据中台-资源调用和算法 |
| TWM592136U (zh) * | 2019-10-21 | 2020-03-11 | 臺灣銀行股份有限公司 | 導引網頁的中台系統 |
| CN111614570B (zh) * | 2020-04-20 | 2022-07-01 | 北京邮电大学 | 一种用于服务网格的流量控制系统及方法 |
| CN111629061B (zh) * | 2020-05-28 | 2023-01-24 | 苏州浪潮智能科技有限公司 | 一种基于Kubernetes的推理服务系统 |
| CN111738757A (zh) * | 2020-06-15 | 2020-10-02 | 中国建设银行股份有限公司 | 一种多渠道服务平台 |
| CN114144761A (zh) * | 2020-06-24 | 2022-03-04 | 京东方科技集团股份有限公司 | 发布系统、推送方法、应用设备、接收装置及服务管理设备 |
| CN112036723A (zh) * | 2020-08-24 | 2020-12-04 | 北京金成顺赢互联网科技有限公司 | 一种企业数字化协同运营中台 |
| CN112015521B (zh) * | 2020-09-30 | 2024-06-07 | 北京百度网讯科技有限公司 | 推理服务的配置方法、装置、电子设备及存储介质 |
| CN112199430A (zh) * | 2020-10-15 | 2021-01-08 | 苏州龙盈软件开发有限公司 | 一种基于数据中台的业务数据处理系统及方法 |
| CN112328656B (zh) * | 2020-11-02 | 2024-06-25 | 中国平安财产保险股份有限公司 | 基于中台架构的服务查询方法、装置、设备及存储介质 |
| CN113472771B (zh) * | 2021-06-29 | 2023-03-24 | 福建华通银行股份有限公司 | 一种智能化中台系统 |
| CN113595926B (zh) * | 2021-07-28 | 2023-04-07 | 南方电网数字电网研究院有限公司 | 基于数据中台的api数据传输方法、装置、设备和介质 |
| CN113806097A (zh) * | 2021-09-29 | 2021-12-17 | 杭州网易云音乐科技有限公司 | 一种数据处理方法、装置、电子设备以及存储介质 |
| CN113868110B (zh) * | 2021-11-30 | 2022-07-12 | 阿里云计算有限公司 | 一种企业数字中台服务健康度的评估方法和装置 |
-
2022
- 2022-01-05 CN CN202210006017.2A patent/CN114036031B/zh active Active
- 2022-12-29 WO PCT/CN2022/143628 patent/WO2023131058A1/zh unknown
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102789394A (zh) * | 2011-05-19 | 2012-11-21 | 阿里巴巴集团控股有限公司 | 一种并行处理消息的方法、装置、节点及服务器集群 |
| US20130110588A1 (en) * | 2011-10-26 | 2013-05-02 | Iex Corporation | Application usage and process monitoring in an enterprise environment |
| CN110324403A (zh) * | 2019-05-23 | 2019-10-11 | 平安科技（深圳）有限公司 | 动态分库路由方法、装置、服务器及存储介质 |
| CN111343275A (zh) * | 2020-03-02 | 2020-06-26 | 北京奇艺世纪科技有限公司 | 资源调度方法和系统 |
| CN111736977A (zh) * | 2020-07-21 | 2020-10-02 | 成都新希望金融信息有限公司 | 一种多中台的中央调度方法及系统 |
| CN112559486A (zh) * | 2020-11-11 | 2021-03-26 | 国网江苏省电力有限公司信息通信分公司 | 一种数据中台统一任务调度管理系统 |
| CN113392158A (zh) * | 2021-06-11 | 2021-09-14 | 中国工商银行股份有限公司 | 业务数据处理方法、装置及数据中台 |
| CN114036031A (zh) * | 2022-01-05 | 2022-02-11 | 阿里云计算有限公司 | 一种企业数字中台中资源服务应用的调度系统和方法 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116700907A (zh) * | 2023-08-04 | 2023-09-05 | 北京国电通网络技术有限公司 | 服务调用需求文档存储方法、装置、电子设备和可读介质 |
| CN116700907B (zh) * | 2023-08-04 | 2023-10-27 | 北京国电通网络技术有限公司 | 服务调用需求文档存储方法、装置、电子设备和可读介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114036031A (zh) | 2022-02-11 |
| CN114036031B (zh) | 2022-06-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2023131058A1 (zh) | 一种企业数字中台中资源服务应用的调度系统和方法 | |
| CN107766129B (zh) | 一种任务处理方法、装置及系统 | |
| CN107423942B (zh) | 一种业务流转的方法及装置 | |
| WO2020024650A1 (zh) | 数据处理方法和装置、客户端 | |
| CN113259359B (zh) | 一种边缘节点能力补充方法、系统、介质及电子终端 | |
| WO2017114176A1 (zh) | 一种分布式环境协调消费队列方法和装置 | |
| US11102284B2 (en) | Service processing methods and systems based on a consortium blockchain network | |
| US11563805B2 (en) | Method, apparatus, client terminal, and server for data processing | |
| CN106533961B (zh) | 一种流量控制方法及装置 | |
| JP6975153B2 (ja) | データ格納サービス処理方法及び装置 | |
| WO2023207082A1 (zh) | 负载均衡方法及装置和电子设备 | |
| CN114598749A (zh) | 一种服务访问方法及装置 | |
| CN109951551B (zh) | 一种容器镜像管理系统及方法 | |
| CN115757611A (zh) | 大数据集群切换方法、装置、电子设备及存储介质 | |
| CN110737425A (zh) | 一种计费平台系统的应用程序的建立方法及装置 | |
| WO2017157111A1 (zh) | 防止内存数据丢失的的方法、装置和系统 | |
| CN110609707B (zh) | 在线数据处理系统生成方法、装置及设备 | |
| CN114710350B (zh) | 一种可调用资源的分配方法、装置、电子设备和存储介质 | |
| CN114710485A (zh) | 处理方法和处理装置 | |
| US10742802B2 (en) | Methods and devices for verifying a communication number | |
| US9184996B2 (en) | Thin client system, management server, client environment management method and program | |
| CN111221858B (zh) | 一种数据处理方法、装置及设备 | |
| CN117040930B (zh) | 区块链网络的资源处理方法、装置、产品、设备和介质 | |
| CN110837458B (zh) | 一种数据平衡验证的方法、设备、及存储介质 | |
| CN110502333B (zh) | 一种访问请求的处理方法和云存储系统 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22918499 Country of ref document: EP Kind code of ref document: A1 |