CN111782363A - Method and flow system for supporting multi-service scene calling - Google Patents
Method and flow system for supporting multi-service scene calling Download PDFInfo
- Publication number
- CN111782363A CN111782363A CN202010612894.5A CN202010612894A CN111782363A CN 111782363 A CN111782363 A CN 111782363A CN 202010612894 A CN202010612894 A CN 202010612894A CN 111782363 A CN111782363 A CN 111782363A
- Authority
- CN
- China
- Prior art keywords
- flow
- execution result
- scene
- service
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
- G06F9/524—Deadlock detection or avoidance
Abstract
The invention discloses a method and a flow system for supporting multi-service scene calling, and relates to the field of application software system development. The method comprises the following steps: the method comprises the steps of establishing connection between a business system and a process system, sending a process scene driving command to the process system by the business system, executing scene driving logic by the process system according to the process scene driving command, executing process data according to an execution result of the scene driving logic, obtaining an execution result of the process data, returning the execution result to the business system, providing service to front ends in a unified mode through a cluster, realizing real-time decision making according to different events and results, and improving the process agility in a multi-business scene.
Description
Technical Field
The invention relates to the field of application software system development, in particular to a method and a flow system for supporting multi-service scene calling.
Background
With the deep development of enterprise services, services of different application scenes are more and more, in the prior art, each service is processed to perform a set of independent process full-life-cycle management, a service system continuously sends a calling request, the process systematic calling request is processed, but a cooperation relation of the content of the process system is not established, the process cannot be reasonably coordinated, each calling request needs to design a process template, the processing process is complicated and repeated, and the waste of the process template resources is caused. So far, no perfect method for realizing calling processing among multi-scenario service flows exists to meet the agility of flows under multi-scenario
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method and a flow system for supporting multi-service scene invocation, aiming at the defects of the prior art.
The technical scheme of the technical problem of the invention is as follows:
a method for supporting multi-service scene calling comprises the following steps:
s1, establishing connection between a service system and a process system, wherein the service system sends a process scene driving command to the process system;
s2, the flow system executes the scene driving logic according to the flow scene driving command, executes the flow data according to the execution result of the scene driving logic, and obtains the execution result of the flow data;
and S3, returning the execution result to the service system.
The invention has the beneficial effects that: according to the scheme, the connection between the service system and the process system is established, the service system sends the process scene driving command to the process system, the process system executes the scene driving logic according to the process scene driving command, executes the process data according to the execution result of the scene driving logic, obtains the execution result of the process data, and returns the execution result to the service system. The process system is deployed on a host as a server, a client of the process system is integrated in a business application program, and the client provides services to a front end in a unified mode through a cluster, so that real-time decision making according to different events and results is realized, and the process agility under a multi-business scene is improved.
Further, the S1 specifically includes: the business system establishes connection with the process system by calling a client API of the process system, and sends a process scene driving command to a server of the process system through the client API.
Further, the S2 specifically includes:
designing a template, logic, rules and execution roles of a flow, and providing the scene driving logic;
and configuring input parameters of the process instance, and driving the process to run according to the configuration parameters and the scene driving logic to obtain an execution result of the process data.
The beneficial effect of adopting the further scheme is that: the scheme provides scene driving logic by designing a template, logic, rules and execution roles of the process, configures input parameters of a process instance, drives the process operation according to the configuration parameters and the scene driving logic, obtains an execution result of process data, realizes the process design supporting multiple service scenes, and provides a process template and a reuse mechanism to support different process design requirements under multiple scenes by designing modules, logics, rules and execution roles of the process.
Further, still include: and monitoring the process data, analyzing the monitored data including the key performance indexes, simulating the process, and feeding back an analysis result.
The beneficial effect of adopting the further scheme is that: the scheme monitors the flow data, analyzes the monitored data including key performance indexes, simulates the flow, feeds back the analysis result, realizes monitoring the flow behavior and automation, knows the running state of the system in real time, finds and solves the problems of the system in time, reduces temporary faults and brings loss.
Further, still include: setting an access threshold value according to business requirements, entering a first preset link when the execution result of preset services in the process data is greater than the threshold value, and entering a second preset link if the execution result of the preset services in the process data is less than the threshold value.
The beneficial effect of adopting the further scheme is that: according to the scheme, the access threshold is set according to the service requirement, so that the resource utilization is optimized, the consistency of the flow is ensured, and deadlock is prevented.
Another technical solution of the present invention for solving the above technical problems is as follows:
a flow system supporting multi-service scenario invocation, comprising: the system comprises a connection establishing module, a flow calling module and a data returning module;
the connection establishing module is used for establishing the connection between the business system and the process system and sending a process scene driving command to the process system;
the flow calling module is used for executing the scene driving logic according to the flow scene driving command, executing the flow data according to the execution result of the scene driving logic and obtaining the execution result of the flow data;
and the data return module is used for returning the execution result to the service system.
The invention has the beneficial effects that: according to the scheme, the connection between the service system and the process system is established, the service system sends the process scene driving command to the process system, the process system executes the scene driving logic according to the process scene driving command, executes the process data according to the execution result of the scene driving logic, obtains the execution result of the process data, and returns the execution result to the service system. The process system is deployed on a host as a server, a client of the process system is integrated in a business application program, and the client provides services to a front end in a unified mode through a cluster, so that real-time decision making according to different events and results is realized, and the process agility under a multi-business scene is improved.
Further, the connection creating module is specifically configured to: the business system establishes connection with the process system by calling a client API of the process system, and sends a process scene driving command to a server of the process system through the client API.
Further, the flow calling module is specifically used for designing a flow template, logic, rules and execution roles and providing the scene driving logic;
and configuring input parameters of the process instance, and driving the process to run according to the configuration parameters and the scene driving logic to obtain an execution result of the process data.
The beneficial effect of adopting the further scheme is that: the scheme provides scene driving logic by designing a template, logic, rules and execution roles of the process, configures input parameters of a process instance, drives the process operation according to the configuration parameters and the scene driving logic, obtains an execution result of process data, realizes the process design supporting multiple service scenes, and provides a process template and a reuse mechanism to support different process design requirements under multiple scenes by designing modules, logics, rules and execution roles of the process.
Further, still include: and the monitoring module is used for monitoring the process data by a user, analyzing the monitored data including the key performance indexes, simulating the process and feeding back an analysis result.
The beneficial effect of adopting the further scheme is that: the scheme monitors the flow data, analyzes the monitored data including key performance indexes, simulates the flow, feeds back the analysis result, realizes monitoring the flow behavior and automation, knows the running state of the system in real time, finds and solves the problems of the system in time, reduces temporary faults and brings loss.
Further, still include: and the access management module is used for setting an access threshold according to business requirements, entering a first preset link when the execution result of the preset service in the process data is greater than the threshold, and entering a second preset link if the execution result of the preset service in the process data is less than the threshold.
The beneficial effect of adopting the further scheme is that: according to the scheme, the access threshold is set according to the service requirement, so that the resource utilization is optimized, the consistency of the flow is ensured, and deadlock is prevented.
Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a schematic flowchart of a method for supporting multiple service scenario calls according to an embodiment of the present invention;
fig. 2 is a block diagram of a flow system supporting multiple service scenario calls according to an embodiment of the present invention.
Detailed Description
The principles and features of this invention are described below in conjunction with the following drawings, which are set forth to illustrate, but are not to be construed to limit the scope of the invention.
As shown in fig. 1, a method for supporting multi-service scenario invocation provided in an embodiment of the present invention includes: s1, establishing connection between the service system and the process system, and sending the process scene driving command to the process system by the service system;
it should be noted that, in an embodiment, the program system is composed of a service end and a client (which part in the diagram is shown), the service layer is deployed independently, and the client provides service application integration in a jar package mode. And the service system calls the server, integrates and calls a client API (application program interface), namely calls a method of the Jar package, establishes connection with the server, and sends a flow scene driving command to the server through the client API.
S2, the flow system executes the scene driving logic according to the scene driving command, and executes the flow data according to the execution result of the scene driving logic to obtain the execution result of the flow data;
and S3, returning the execution result to the service system.
It should be noted that the process system is deployed on the host as a server, a client of the process system is integrated in a business application program, the server supports multi-node distributed deployment, and can be deployed in various environments such as a physical machine, a virtual machine, a container platform, and the like, and a pair of front ends are uniformly provided with services through a cluster mode. The hardware configuration may be: x86 server, at least 1; CPU 2C2 GHz; a memory 4 GB; 20GB of a magnetic disk; the network depends on the service requirement, and the gigabit network is recommended to ensure the scheme effect.
According to the scheme, the connection between the service system and the process system is established, the service system sends the process scene driving command to the process system, the process system executes the scene driving logic according to the process scene driving command, executes the process data according to the execution result of the scene driving logic, obtains the execution result of the process data, and returns the execution result to the service system. The process system is deployed on a host as a server, a client of the process system is integrated in a business application program, and the client provides services to a front end in a unified mode through a cluster, so that real-time decision making according to different events and results is realized, and the process agility under a multi-business scene is improved.
Preferably, in any of the above embodiments, S1 specifically includes: the business system establishes connection with the process system by calling a client API of the process system, and sends a process scene driving command to a server of the process system through the client API.
Preferably, in any of the above embodiments, S2 specifically includes:
designing a template, logic, rules and execution roles of the process, and providing scene driving logic;
it should be noted that the flow system includes a flow design module, which is used to design the flow template, logic, rules and execution roles, and provide the flow template and reuse mechanism.
And configuring input parameters of the process instance, driving the process to run according to the configuration parameters and the scene driving logic, and obtaining an execution result of the process data.
It should be noted that, in a certain embodiment, the process configuration module of the process system binds participants to the operation of the process instance, allocates resources, sets other specific parameters, such as a mobile phone number, an identity card, and the like, and may also configure other required parameters according to the service requirement.
It should be noted that, in a certain embodiment, a process engine of the process system drives the operation of the process and is responsible for maintaining process data, managing the state of the process, and implementing transaction management of the process, and for a distributed process, interaction and coordination with other engines are required, for example: the management systems are provided with a plurality of engines, and the plurality of engines coordinate operations of the same process, such as a execution, b non-execution or a non-execution, b execution and the like.
It should be noted that, in an embodiment, a centralized storage place is provided for the processes and the knowledge related to the processes, and a process repository is provided for directory service to facilitate query and release of the processes.
The scheme provides scene driving logic by designing a template, logic, rules and execution roles of the process, configures input parameters of a process instance, drives the process operation according to the configuration parameters and the scene driving logic, obtains an execution result of process data, realizes the process design supporting multiple service scenes, and provides a process template and a reuse mechanism to support different process design requirements under multiple scenes by designing modules, logics, rules and execution roles of the process.
Preferably, in any of the above embodiments, further comprising: monitoring the process data, analyzing the monitored data including key performance indexes, simulating the process, and feeding back the analysis result.
It should be noted that monitoring the flow data may include calling a record, monitoring an operation state, capturing error information, and sending a prompt message.
It should be noted that, in a certain embodiment, data of a key performance index, such as the number of calls, the number of errors, the usage rate of host space, the proportion of memory space, and the like, is analyzed, parameters that affect performance are analyzed, resource optimization is performed, consistency of a flow is ensured, and deadlock is prevented.
The scheme monitors the flow data, analyzes the monitored data including key performance indexes, simulates the flow, feeds back the analysis result, realizes monitoring the flow behavior and automation, knows the running state of the system in real time, finds and solves the problems of the system in time, reduces temporary faults and brings loss.
Preferably, in any of the above embodiments, further comprising: and setting an access threshold according to the service requirement, entering a first preset link when the execution result of the preset service in the process data is greater than the threshold, and entering a second preset link if the execution result of the preset service in the process data is less than the threshold.
According to the scheme, the access threshold is set according to the service requirement, so that the resource utilization is optimized, the consistency of the flow is ensured, and deadlock is prevented.
In one embodiment, as shown in fig. 2, a flow system supporting multi-service scenario invocation includes: the system comprises a connection creating module 11, a flow calling module 12 and a data returning module 13;
the connection creating module 11 is configured to create a connection between the service system and the process system, and send a process scene driving command to the process system;
the flow calling module 12 is configured to execute the scene driving logic according to the flow scene driving command, execute the flow data according to an execution result of the scene driving logic, and obtain an execution result of the flow data;
the data returning module 13 is used for returning the execution result to the service system.
According to the scheme, the connection between the service system and the process system is established, the service system sends the process scene driving command to the process system, the process system executes the scene driving logic according to the process scene driving command, executes the process data according to the execution result of the scene driving logic, obtains the execution result of the process data, and returns the execution result to the service system. The process system is deployed on a host as a server, a client of the process system is integrated in a business application program, and the client provides services to a front end in a unified mode through a cluster, so that real-time decision making according to different events and results is realized, and the process agility under a multi-business scene is improved.
Preferably, in any of the above embodiments, the connection creating module 11 is specifically configured to: the business system establishes connection with the process system by calling a client API of the process system, and sends a process scene driving command to a server of the process system through the client API.
Preferably, in any of the above embodiments, the flow calling module 12 is specifically configured to design a template, logic, rule and execution role of the flow, and provide a scene driving logic;
and configuring input parameters of the process instance, driving the process to run according to the configuration parameters and the scene driving logic, and obtaining an execution result of the process data.
The scheme provides scene driving logic by designing a template, logic, rules and execution roles of the process, configures input parameters of a process instance, drives the process operation according to the configuration parameters and the scene driving logic, obtains an execution result of process data, realizes the process design supporting multiple service scenes, and provides a process template and a reuse mechanism to support different process design requirements under multiple scenes by designing modules, logics, rules and execution roles of the process.
Preferably, in any of the above embodiments, further comprising: and the monitoring module is used for monitoring the process data by a user, analyzing the monitored data including the key performance indexes, simulating the process and feeding back the analysis result.
The scheme monitors the flow data, analyzes the monitored data including key performance indexes, simulates the flow, feeds back the analysis result, realizes monitoring the flow behavior and automation, knows the running state of the system in real time, finds and solves the problems of the system in time, reduces temporary faults and brings loss.
Preferably, in any of the above embodiments, further comprising: and the access management module is used for setting an access threshold according to the business requirement, entering a first preset link when the execution result of the preset service in the process data is greater than the threshold, and entering a second preset link if the execution result of the preset service in the process data is less than the threshold.
According to the scheme, the access threshold is set according to the service requirement, so that the resource utilization is optimized, the consistency of the flow is ensured, and deadlock is prevented.
It is understood that some or all of the alternative embodiments described above may be included in some embodiments.
It should be noted that the above embodiments are product embodiments corresponding to the previous method embodiments, and for the description of each optional implementation in the product embodiments, reference may be made to corresponding descriptions in the above method embodiments, and details are not described here again.
The reader should understand that in the description of this specification, reference to the description of the terms "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described method embodiments are merely illustrative, and for example, the division of steps into only one logical functional division may be implemented in practice in another way, for example, multiple steps may be combined or integrated into another step, or some features may be omitted, or not implemented.
The above method, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
While the invention has been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for supporting multi-service scene calling, comprising:
s1, establishing connection between a service system and a process system, wherein the service system sends a process scene driving command to the process system;
s2, the flow system executes the scene driving logic according to the flow scene driving command, executes the flow data according to the execution result of the scene driving logic, and obtains the execution result of the flow data;
and S3, returning the execution result to the service system.
2. The method for supporting multi-service scenario invocation according to claim 1, wherein said S1 specifically includes: the business system establishes connection with the process system by calling a client API of the process system, and sends a process scene driving command to a server of the process system through the client API.
3. The method for supporting multi-service scenario invocation according to claim 1, wherein said S2 specifically includes:
designing a template, logic, rules and execution roles of a flow, and providing the scene driving logic;
and configuring input parameters of the process instance, and driving the process to run according to the configuration parameters and the scene driving logic to obtain an execution result of the process data.
4. The method for supporting multiple service scenario calls according to any of claims 1-3, further comprising:
and monitoring the process data, analyzing the monitored data including the key performance indexes, simulating the process, and feeding back an analysis result.
5. The method for supporting multiple service scenario calls according to any of claims 1-3, further comprising: setting an access threshold value according to business requirements, entering a first preset link when the execution result of preset services in the process data is greater than the threshold value, and entering a second preset link if the execution result of the preset services in the process data is less than the threshold value.
6. A flow system supporting multi-service scene calling is characterized by comprising: the system comprises a connection establishing module, a flow calling module and a data returning module;
the connection establishing module is used for establishing the connection between the business system and the process system and sending a process scene driving command to the process system;
the flow calling module is used for executing the scene driving logic according to the flow scene driving command, executing the flow data according to the execution result of the scene driving logic and obtaining the execution result of the flow data;
and the data return module is used for returning the execution result to the service system.
7. The flow system supporting multi-service scenario invocation according to claim 6, wherein said connection creation module is specifically configured to: the business system establishes connection with the process system by calling a client API of the process system, and sends a process scene driving command to a server of the process system through the client API.
8. The flow system supporting multi-service scenario invocation according to claim 6, wherein said flow invocation module is specifically configured to design flow templates, logic, rules and execution roles, and provide said scenario-driven logic;
and configuring input parameters of the process instance, and driving the process to run according to the configuration parameters and the scene driving logic to obtain an execution result of the process data.
9. The flow system supporting multiple service scenario calls as claimed in any one of claims 6 to 8, further comprising: and the monitoring module is used for monitoring the process data by a user, analyzing the monitored data including the key performance indexes, simulating the process and feeding back an analysis result.
10. The flow system supporting multiple service scenario calls as claimed in any one of claims 6 to 8, further comprising: and the access management module is used for setting an access threshold according to business requirements, entering a first preset link when the execution result of the preset service in the process data is greater than the threshold, and entering a second preset link if the execution result of the preset service in the process data is less than the threshold.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010612894.5A CN111782363A (en) | 2020-06-29 | 2020-06-29 | Method and flow system for supporting multi-service scene calling |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010612894.5A CN111782363A (en) | 2020-06-29 | 2020-06-29 | Method and flow system for supporting multi-service scene calling |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111782363A true CN111782363A (en) | 2020-10-16 |
Family
ID=72761235
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010612894.5A Pending CN111782363A (en) | 2020-06-29 | 2020-06-29 | Method and flow system for supporting multi-service scene calling |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111782363A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377371A (en) * | 2021-06-02 | 2021-09-10 | 五八到家有限公司 | Multi-scene configuration method, system, device and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101800762A (en) * | 2009-12-30 | 2010-08-11 | 中兴通讯股份有限公司 | Service cloud system for fusing multiple services and service implementation method |
| WO2017109791A1 (en) * | 2015-12-22 | 2017-06-29 | Tangirala Srinivas | A system and method for building enterprise applications |
| CN110147229A (en) * | 2019-05-24 | 2019-08-20 | 利姆斯(北京)区块链技术有限公司 | Flow engine system, method for processing business and device |
| CN110991977A (en) * | 2019-10-10 | 2020-04-10 | 广州供电局有限公司 | Collaborative scene intelligent monitoring system based on power grid business process |
| CN111242400A (en) * | 2018-11-29 | 2020-06-05 | 上海昶铭软件科技有限公司 | Business process management system and working method thereof |
-
2020
- 2020-06-29 CN CN202010612894.5A patent/CN111782363A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101800762A (en) * | 2009-12-30 | 2010-08-11 | 中兴通讯股份有限公司 | Service cloud system for fusing multiple services and service implementation method |
| WO2017109791A1 (en) * | 2015-12-22 | 2017-06-29 | Tangirala Srinivas | A system and method for building enterprise applications |
| CN111242400A (en) * | 2018-11-29 | 2020-06-05 | 上海昶铭软件科技有限公司 | Business process management system and working method thereof |
| CN110147229A (en) * | 2019-05-24 | 2019-08-20 | 利姆斯(北京)区块链技术有限公司 | Flow engine system, method for processing business and device |
| CN110991977A (en) * | 2019-10-10 | 2020-04-10 | 广州供电局有限公司 | Collaborative scene intelligent monitoring system based on power grid business process |
Non-Patent Citations (1)
| Title |
|---|
| 刘涛: "《基于统一流程引擎的公文系统设计及实现》", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377371A (en) * | 2021-06-02 | 2021-09-10 | 五八到家有限公司 | Multi-scene configuration method, system, device and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10033597B2 (en) | Type-to-type analysis for cloud computing technical components with translation scripts | |
| US10824474B1 (en) | Dynamically allocating resources for interdependent portions of distributed data processing programs | |
| CN110740053B (en) | Service arranging method and device | |
| US7451201B2 (en) | Policy driven autonomic computing-specifying relationships | |
| US8285827B1 (en) | Method and apparatus for resource management with a model-based architecture | |
| CN105119966A (en) | Official account management method and device | |
| CN103297485B (en) | Distributed caching automated management system and distributed caching automatic management method | |
| CN103176892A (en) | Page monitoring method and system | |
| CN103581332A (en) | HDFS framework and pressure decomposition method for NameNodes in HDFS framework | |
| US8631062B2 (en) | Managing distributed resources in a computer system | |
| CN102457578A (en) | Distributed network monitoring method based on event mechanism | |
| CN111400011A (en) | Real-time task scheduling method, system, equipment and readable storage medium | |
| CN114090580A (en) | Data processing method, device, equipment, storage medium and product | |
| CN114706690B (en) | Method and system for sharing GPU (graphics processing Unit) by Kubernetes container | |
| US20220182851A1 (en) | Communication Method and Apparatus for Plurality of Administrative Domains | |
| CN111782363A (en) | Method and flow system for supporting multi-service scene calling | |
| Chazalet | Service level agreements compliance checking in the cloud computing: architectural pattern, prototype, and validation | |
| CN115964176B (en) | Cloud computing cluster scheduling method, electronic equipment and storage medium | |
| CN113722114A (en) | Data service processing method and device, computing equipment and storage medium | |
| CN116719623A (en) | Job scheduling method, job result processing method and device | |
| CN115037757B (en) | Multi-cluster service management system | |
| CN115629860A (en) | Software parameter tuning method, container management platform, storage medium and system | |
| WO2021036987A1 (en) | Method and device for achieving operation and maintenance monitoring | |
| US11836125B1 (en) | Scalable database dependency monitoring and visualization system | |
| CN110019113B (en) | Database service processing method and database server |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201016 |