CN114444136A - Method and system for decoupling computing engine and platform - Google Patents
Method and system for decoupling computing engine and platform Download PDFInfo
- Publication number
- CN114444136A CN114444136A CN202210119038.5A CN202210119038A CN114444136A CN 114444136 A CN114444136 A CN 114444136A CN 202210119038 A CN202210119038 A CN 202210119038A CN 114444136 A CN114444136 A CN 114444136A
- Authority
- CN
- China
- Prior art keywords
- interaction
- node
- platform
- computing engine
- driver
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 97
- 230000003993 interaction Effects 0.000 claims abstract description 209
- 230000008569 process Effects 0.000 claims abstract description 20
- 230000006399 behavior Effects 0.000 claims abstract description 18
- 230000006870 function Effects 0.000 claims description 81
- 230000002452 interceptive effect Effects 0.000 claims description 26
- 238000012545 processing Methods 0.000 claims description 16
- 238000004891 communication Methods 0.000 claims description 10
- 230000036541 health Effects 0.000 claims description 10
- 238000011161 development Methods 0.000 claims description 5
- 238000011084 recovery Methods 0.000 claims description 4
- 238000001514 detection method Methods 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 238000013500 data storage Methods 0.000 abstract description 9
- 230000010354 integration Effects 0.000 abstract description 5
- 238000013461 design Methods 0.000 description 8
- 230000006978 adaptation Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 230000001960 triggered effect Effects 0.000 description 6
- 230000009471 action Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
-
- 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/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method and a system for decoupling a computing engine and a platform, wherein the computing engine is designed by adopting a driver-master-worker structure, when the computing engine triggers an interaction (such as event interaction among multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), the corresponding interaction triggering node (worker or master) can report the interaction information, so that a functional module can process corresponding interaction behaviors according to service codes corresponding to the interaction information, the decoupling of active triggering interaction of the computing engine can be realized, after the decoupling, the computing engine is adapted by a platform manufacturer when integrated, and the computing engine does not need to be adapted. Therefore, in the method of the embodiment of the application, in the use scene of interconnection, the computing engine can be integrated through a general integration method.
Description
Technical Field
The application relates to the field of privacy computing, in particular to a method and a system for decoupling a computing engine and a platform.
Background
In the field of privacy computing, product computing engines are respectively realized, the computing engines and platforms are mutually coupled, the computing engines and platforms of different manufacturers are difficult to integrate with each other (for example, the computing engine of company a is difficult to be integrated and called by the platform of company B), and interconnection and intercommunication are difficult to achieve. In the functional level, the computing engine can realize the functions of registration discovery, health check, fault removal, fault recovery, system health, system alarm and the like of computing resources (worker, slave nodes) in the computing engine through a Master-worker structure, and can also realize the functions of task load balance scheduling of federal learning or multi-party safety computation, routing distribution of interaction events among nodes according to task id and the like, thereby realizing the decoupling of the functional level.
When a computing engine is called to perform computing tasks, an extended driver-master-worker structure can be adopted, a driver layer is actually a client, an sdk-level development kit is provided, and platform developers can easily call the functions of the driver according to developer documents of the development kit, so that the functions of the whole computing engine are called, and interconnection and intercommunication of different platforms when the computing engines are called can be realized through a uniform sdk calling mode.
In privacy computing, there is another class of interactions, triggered by the compute engine, such as: 1. in the task process, cross-node event interaction exists among multiple nodes, and multiple nodes are often positioned in respective local area network inner networks to cause that the nodes cannot be directly connected and need to be transferred through a platform; 2. temporary information needs to be stored in a platform in the task process; 3. when the task is finished, each party stores the result to the storage and needs to report the file _ id of the result in the storage to the platform; 4. after the task is finished, the state of the whole task needs to be reported to the platform; 5. various problems occur in the computing resources, when the master needs to report an alarm to the platform, and the like. The interaction mode of the part is not defined by a computing engine, but is defined by platforms of different manufacturers according to self specifications, so that the computing engine can only realize different interaction modes according to different customers and cannot be universal in the current interconnection implementation.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method and a system for decoupling a computing engine from a platform, so as to solve a problem that, for interaction actively triggered by the computing engine, in an existing interconnection implementation manner, the computing engine can only implement different interaction methods according to different clients, and cannot be used universally.
The method for decoupling the computing engine and the platform is applied to a plurality of platform parties participating in interaction, for each platform party, a function module is arranged between a driver node and the platform of the computing engine, the function module integrates service codes related to platform functions, and the computing engine further comprises a master node and a worker node;
a method for decoupling a computing engine from a platform specifically comprises the following steps:
when a computing engine actively triggers event interaction, a master node or a worker node which triggers the interaction reports interaction information;
and processing the corresponding interaction behavior by the functional module according to the service code corresponding to the interaction information, and realizing the decoupling of the computing engine and the platform.
In the technical scheme, a driver-master-worker structure is adopted to design the computing engine, when the computing engine triggers an interaction (such as event interaction among multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), the corresponding interaction triggering node (worker or master) reports the interaction information, so that the functional module can process the corresponding interaction behavior according to the service code corresponding to the interaction information, decoupling of active triggering interaction of the computing engine can be realized, after decoupling, the computing engine is integrated, a platform manufacturer carries out adaptation, and the computing engine does not need to carry out adaptation. Therefore, in the method of the embodiment of the application, in the use scene of interconnection, the computing engine can be integrated through a general integration method.
In some optional embodiments, the function module is further configured to set a callback of the driver node;
before the functional module processes the corresponding interactive behavior according to the service code corresponding to the interactive information, the method further comprises the following steps:
the master node or the worker node which triggers interaction reports the interaction information to the driver node;
receiving the interactive information by a driver node;
and calling the callback corresponding to the interaction of the functional module by the driver node according to the interaction information.
In the technical scheme, a driver-master-worker structure is adopted to design a computing engine, and a series of methods or functions are provided in a driver node and used for setting callbacks (callbacks) of various interactions which need to be actively triggered by the computing engine. When a computing engine triggers an interaction (such as event interaction between multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), a corresponding interaction triggering node (worker or master) informs a driver node of the content of the interaction, the driver calls a preset callback method or function for processing the corresponding interaction, and the specific processing logic of the callback method or function is realized by a functional module of a platform side, so that decoupling between the computing engine and the platform when the computing engine actively triggers the interaction is realized.
In some optional embodiments, the driver node is used for instructing the platform side to set the callback of the driver node by developing the functional module.
In the technical scheme, in order to realize the process that the driver calls the callback method or the function which is set in advance and used for processing the corresponding interaction, the driver node is used for indicating the platform side to set the callback of the driver node by developing the functional module.
In some optional embodiments, the callback of the driver node may be a callback method or function; the callback of the driver node can also be a network communication interface address, such as an http url address, and the decoupling of the computing engine and the platform can also be achieved by standardizing the callback network communication interface address and sending and receiving data formats.
In some optional embodiments, the driver node provides a series of normative interfaces that inform the platform side of the method and specification of the set callback in a way of a public document.
In the technical scheme, a series of normative interfaces are provided in the driver node and are used for setting a callback method or function for actively triggering interaction by each manufacturer platform. And a normative interface provided by the Driver node informs each factory platform how to set a callback method or function and the specification of the callback method or function in a public document mode.
In some optional embodiments, before the compute engine actively triggers the event interaction, further:
for each platform side, developing a functional module corresponding to a platform service code based on a driver node;
and when the functional module is initialized, calling the callback setting method and specification provided by the driver node, and setting the callback of the driver node.
Among the above-mentioned technical scheme, different producers accomplish functional logic according to the standardization file that driver node provided, the function module of developer oneself, and function module inside contains 2 partial functions: 1. the platform may invoke the functionality of the compute engine through the function module (the interaction is initiated actively by the platform). 2. The function module sets a callback method and a function in the driver node, and when the computing engine actively interacts, the driver calls the callback method and the function set by the function module to respond to the interaction (the computing engine actively initiates the interaction).
In some optional embodiments, the functional module further integrates the functions of acquisition registration algorithm, initiation task and event communication of the computing engine.
In some alternative embodiments, the method comprises:
the master node is used for performing the functions of registering discovery, health detection, fault removal, fault recovery, system health and system alarm of computing resources, and is used for performing task load balancing scheduling of federal learning or multi-party safety computation, inter-node interaction events or routing distribution according to distribution events, so that the decoupling of the functional level is realized.
In the technical scheme, the decoupling of the functions of the computing engine, such as the registration of computing resources, health check, fault removal, task scheduling and the like, can be realized through a master-worker structure.
In some alternative embodiments, the method comprises:
when a computing engine is called to perform computing tasks, the function of a driver is called according to a developer document of a development kit, so that the function of the whole computing engine is called, a standard interface is defined by the driver, and the driver calls different platform parties, so that decoupling can be realized.
In the technical scheme, the platform calls decoupling of the computing engine, for example, the platform initiates a task, forwards a task event and the like, the decoupling can be called by different platform manufacturers through a driver-master-worker structure and a driver-defined standard interface, and the decoupling can be realized.
In some optional embodiments, before the functional module processes the corresponding interaction behavior according to the service code corresponding to the interaction information, the method further includes:
when a computing engine actively triggers event interaction, a master node or a worker node which triggers the interaction reports interaction information;
receiving, by the middleware, the interaction information;
the functional module acquires the interaction information from the middleware so as to execute subsequent logic of interaction through the functional module and realize decoupling of the computing engine and the platform.
In the above technical solution, when deploying, a middleware module, such as a Message Queue (MQ), is added. In a scenario with a higher security level, such as a manufacturer of a bank or a government system, a message middleware self-developed by the manufacturer may be used. When the computing engine triggers active interaction, the interaction information can be stored in the middleware, and the data format stored in the middleware is used as a public document. When different manufacturers realize the functional modules, the corresponding interaction information can be obtained from the middleware, and after analysis, the functional modules can be used for subsequent functional logic realization. In the mode, a callback mechanism of a driver to the functional module is not needed, and the decoupling between the computing engine and the platform can be realized when the computing engine actively triggers the interaction. Wherein, different producers according to the standardization file that driver node provided and the standardization file of the data format of the middleware of relying on, the functional module of developer producer oneself accomplishes functional logic, and the functional module inside contains 2 partial functions: 1. the platform may invoke the functionality of the compute engine through the function module (the interaction is initiated actively by the platform). 2. When the computing engine actively interacts, the functional module acquires the data stored in the middleware, analyzes the data format, and then processes the corresponding interaction event (the computing engine actively initiates the interaction).
The system for decoupling a computing engine and a platform provided by the embodiment of the application comprises:
the master node and the worker node are used for reporting the interaction information by the master node or the worker node which triggers the interaction when the computing engine actively triggers the event interaction;
and the functional module integrates service codes related to platform functions, and is used for processing corresponding interactive behaviors according to the service codes corresponding to the interactive information so as to realize the decoupling of the computing engine and the platform.
In the technical scheme, a driver-master-worker structure is adopted to design the computing engine, when the computing engine triggers an interaction (such as event interaction among multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), the corresponding interaction triggering node (worker or master) reports the interaction information, so that the functional module can process the corresponding interaction behavior according to the service code corresponding to the interaction information, decoupling of active triggering interaction of the computing engine can be realized, after decoupling, the computing engine is integrated, a platform manufacturer carries out adaptation, and the computing engine does not need to carry out adaptation. Therefore, in the method of the embodiment of the application, in the use scene of interconnection, the computing engine can be integrated through a general integration method.
In some optional embodiments, further comprising:
and the driver node is used for receiving the interaction information reported by the master node or the worker node and calling a callback corresponding to interaction of the functional module according to the interaction information.
In the technical scheme, a driver-master-worker structure is adopted to design the computing engine, and a series of methods or functions are provided in a driver node and used for setting callbacks (callbacks) of interactions which need to be actively triggered by the computing engine. When a computing engine triggers an interaction (such as event interaction between multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), a corresponding interaction triggering node (worker or master) informs a driver node of the content of the interaction, the driver calls a preset callback method or function for processing the corresponding interaction, and the specific processing logic of the callback method or function is realized by a functional module of a platform side, so that decoupling between the computing engine and the platform when the computing engine actively triggers the interaction is realized.
In some optional embodiments, further comprising: the middleware is used for storing the interaction information;
the master node and the worker node are also used for informing the middleware of the interaction information by the master node or the worker node which triggers the interaction when the computing engine actively triggers the event interaction;
the function module is also used for acquiring the interaction information from the middleware.
In the above technical solution, when deploying, a middleware module, such as a Message Queue (MQ), is added. In a scenario with a higher security level, such as a manufacturer of a bank or a government system, a message middleware self-developed by the manufacturer may be used. When the computing engine triggers active interaction, the interaction information can be stored in the middleware, and the data format stored in the middleware is used as a public document. When different manufacturers realize the functional modules, the corresponding interaction information can be obtained from the middleware, and after analysis, the functional modules can be used for subsequent functional logic realization. In the mode, a callback mechanism of a driver to the functional module is not needed, and the decoupling between the computing engine and the platform can be realized when the computing engine actively triggers the interaction. Wherein, different producers according to the standardization file that driver node provided and the standardization file of the data format of the middleware of relying on, the functional module of developer producer oneself accomplishes functional logic, and the functional module inside contains 2 partial functions: 1. the platform may invoke the functionality of the compute engine through the function module (the interaction is initiated actively by the platform). 2. When the computing engine actively interacts, the functional module acquires the data stored in the middleware, analyzes the data format, and then processes the corresponding interaction event (the computing engine actively initiates the interaction).
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
FIG. 1 is a flowchart of method steps for decoupling a compute engine from a platform according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a system in which a computing engine is decoupled from a platform according to an embodiment of the present application;
FIG. 3 is a schematic workflow diagram of a system in which a compute engine is decoupled from a platform according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a system in which a computing engine is decoupled from a platform according to another embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The method for decoupling the computing engine and the platform is applied to a plurality of platform sides participating in interaction, for each platform side, a function module is arranged between a driver node of the computing engine and the platform, the function module integrates service codes related to platform functions, and the computing engine further comprises a master node and a worker node.
Referring to fig. 1, fig. 1 is a flowchart illustrating steps of a method for decoupling a computing engine from a platform, which specifically includes:
step 100, when a computing engine actively triggers event interaction, a master node or a worker node which triggers the interaction reports interaction information;
and 200, processing corresponding interactive behaviors by the functional module according to the service codes corresponding to the interactive information, and realizing the decoupling of the computing engine and the platform.
In the embodiment of the application, a driver-master-worker structure is adopted to design a computing engine, when the computing engine triggers an interaction (such as event interaction among multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), the corresponding interaction triggering node (worker or master) can report the interaction information, so that a functional module can process corresponding interaction behaviors according to service codes corresponding to the interaction information, decoupling of active triggering interaction of the computing engine can be realized, after decoupling, when the computing engine is integrated, adaptation is carried out by a platform manufacturer, and the computing engine does not need to be adapted. Therefore, in the method of the embodiment of the application, in the use scene of interconnection, the computing engine can be integrated through a general integration method.
In some optional embodiments, the function module is further configured to set a callback of the driver node; before the functional module processes the corresponding interactive behavior according to the service code corresponding to the interactive information, the method also comprises the following steps 101-103:
step 101, a master node or a worker node which triggers interaction reports interaction information to a driver node;
102, receiving interactive information by a driver node;
and 103, calling a callback corresponding to interaction of the functional module by the driver node according to the interaction information.
In the embodiment of the application, a driver-master-worker structure is adopted to design a computing engine, and a series of methods or functions are provided in a driver node and used for setting callbacks (callbacks) of various interactions which need to be actively triggered by the computing engine. When a computing engine triggers an interaction (such as event interaction between multiple nodes, temporary data storage, result reporting, state reporting, alarm notification, and the like), a corresponding interaction-triggering node (worker or master) informs a driver node of the content of the interaction, the driver calls a preset callback method or function for processing the corresponding interaction, and the specific processing logic of the callback method or function is realized by a function module of the platform side, so that decoupling between the computing engine and the platform when the computing engine actively triggers the interaction is realized.
In some optional embodiments, the driver node is used for instructing the platform side to set the callback of the driver node by developing the functional module.
In the embodiment of the application, in order to realize the process that the driver calls the callback method or the function which is set in advance and used for processing the corresponding interaction, the driver node is used for indicating the platform side to set the callback of the driver node by developing the functional module.
In some optional embodiments, the callback of the driver node may be a callback method or function; the callback of the driver node can also be a network communication interface address, such as an http url address, and the decoupling of the computing engine and the platform can also be achieved by standardizing the callback network communication interface address and sending and receiving data formats.
In some optional embodiments, the driver node provides a series of normative interfaces that inform the platform side of the method and specification of the set callback in a way of a public document.
In the embodiment of the application, a driver node provides a series of normative interfaces for each manufacturer platform to set a callback method or function for actively triggering interaction. And a normative interface provided by the Driver node informs each factory platform how to set a callback method or function and the specification of the callback method or function in a public document mode.
In some optional embodiments, before the compute engine actively triggers the event interaction, further:
for each platform side, developing a functional module corresponding to a platform service code based on a driver node;
and when the functional module is initialized, calling the callback setting method and specification provided by the driver node, and setting the callback of the driver node.
In this application embodiment, different producers accomplish the functional logic according to the normative file that driver node provided, developer producer's own functional module, and the inside 2 partial functions that contain of functional module: 1. the platform may invoke the functionality of the compute engine through the function module (the interaction is initiated actively by the platform). 2. The function module sets a callback method and a function in the driver node, and when the computing engine actively interacts, the driver calls the callback method and the function set by the function module to respond to the interaction (the computing engine actively initiates the interaction).
In some optional embodiments, the functional module further integrates the functions of acquisition registration algorithm, initiation task and event communication of the computing engine.
In some alternative embodiments, the method comprises:
the master node is used for performing the functions of registering discovery, health detection, fault removal, fault recovery, system health and system alarm of computing resources, and is used for performing task load balancing scheduling of federal learning or multi-party safety computation, inter-node interaction events or routing distribution according to distribution events, so that the decoupling of the functional level is realized.
In the embodiment of the application, decoupling on functions of the computing engine, such as registration of computing resources, health check, fault removal, task scheduling and the like, can be realized through a master-worker structure.
In some alternative embodiments, the method comprises:
when a computing engine is called to perform computing tasks, the function of a driver is called according to a developer document of a development kit, so that the function of the whole computing engine is called, a standard interface is defined by the driver, and the driver calls different platform parties, so that decoupling can be realized.
In the embodiment of the application, the platform calls decoupling of the computing engine, for example, the platform initiates a task, forwards a task event and the like, the decoupling can be realized by calling different platform manufacturers through a driver-master-worker structure and a driver-defined standard interface.
In some optional embodiments, before the functional module processes the corresponding interactive behavior according to the service code corresponding to the interactive information, the method further includes steps 111 to 113:
step 111, when the computing engine actively triggers event interaction, a master node or a worker node which triggers the interaction reports interaction information;
step 112, receiving the interactive information by the middleware;
and 113, the functional module acquires interaction information from the middleware to execute subsequent logic of interaction through the functional module, so that decoupling of the computing engine and the platform is realized.
In the embodiment of the application, a middleware module, such as a Message Queue (MQ) and the like, is added during deployment. In a scenario with a higher security level, such as a manufacturer of a bank or a government system, a message middleware self-developed by the manufacturer may be used. When the computing engine triggers active interaction, the interaction information can be stored in the middleware, and the data format stored in the middleware is used as a public document. When different manufacturers realize the functional modules, the corresponding interaction information can be obtained from the middleware, and after analysis, the functional modules can be used for subsequent functional logic realization. In the mode, a callback mechanism of a driver to the functional module is not needed, and the decoupling between the computing engine and the platform can be realized when the computing engine actively triggers the interaction. Wherein, different producers according to the standardization file that driver node provided and the standardization file of the data format of the middleware of relying on, the functional module of developer producer oneself accomplishes functional logic, and the functional module inside contains 2 partial functions: 1. the platform may invoke the functionality of the compute engine through the function module (the interaction is initiated actively by the platform). 2. When the computing engine actively interacts, the functional module acquires the data stored in the middleware, analyzes the data format, and then processes the corresponding interaction event (the computing engine actively initiates the interaction).
Referring to fig. 2, fig. 2 is a schematic structural diagram of a system for decoupling a computing engine from a platform according to an embodiment of the present application, including:
the master node and the worker node are used for reporting the interaction information by the master node or the worker node which triggers the interaction when the computing engine actively triggers the event interaction;
and the functional module integrates service codes related to platform functions, and is used for processing corresponding interactive behaviors according to the service codes corresponding to the interactive information so as to realize the decoupling of the computing engine and the platform.
In the embodiment of the application, a driver-master-worker structure is adopted to design a computing engine, when the computing engine triggers an interaction (such as event interaction among multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), the corresponding interaction triggering node (worker or master) can report the interaction information, so that a functional module can process corresponding interaction behaviors according to service codes corresponding to the interaction information, decoupling of active triggering interaction of the computing engine can be realized, after decoupling, when the computing engine is integrated, adaptation is carried out by a platform manufacturer, and the computing engine does not need to be adapted. Therefore, in the method of the embodiment of the application, in the use scene of interconnection, the computing engine can be integrated through a general integration method.
In some optional embodiments, further comprising: and the driver node is used for receiving the interaction information reported by the master node or the worker node and calling a callback corresponding to interaction of the functional module according to the interaction information.
In the embodiment of the application, a driver-master-worker structure is adopted to design a computing engine, and a series of methods or functions are provided in a driver node and used for setting callbacks (callbacks) of various interactions which need to be actively triggered by the computing engine. When a computing engine triggers an interaction (such as event interaction between multiple nodes, temporary data storage, result reporting, state reporting, alarm notification and the like), a corresponding interaction triggering node (worker or master) informs a driver node of the content of the interaction, the driver calls a preset callback method or function for processing the corresponding interaction, and the specific processing logic of the callback method or function is realized by a functional module of a platform side, so that decoupling between the computing engine and the platform when the computing engine actively triggers the interaction is realized.
Referring to fig. 3, fig. 3 is a schematic workflow diagram of a system for decoupling a computing engine from a platform in an embodiment of the present application, which specifically includes:
before the computing engine actively triggers event interaction, a driver node is utilized to provide a series of normative interfaces which inform a platform side of a method and specification for setting callback in a public document mode. For each platform side, developing a function module corresponding to a platform service code based on a driver node, calling a callback setting method and specification provided by the driver node when the function module is initialized, and setting the callback of the driver node.
When the computing engine actively triggers event interaction, a master node or a worker node which triggers the interaction reports interaction information to a driver node; receiving the interactive information by a driver node; and calling the callback corresponding to the interaction of the functional module by the driver node according to the interaction information.
And then, the functional module processes the corresponding interaction behavior according to the service code corresponding to the interaction information, and the decoupling of the computing engine and the platform is realized.
And finally, returning the original link of the interactive structure, returning the interactive result of the functional module to the driver node, and returning the driver node to the master node or the worker node which triggers the interaction.
In some optional embodiments, please refer to fig. 4, where fig. 4 is a schematic structural diagram of a system for decoupling a computing engine from a platform according to another embodiment of the present application, and the system further includes: the middleware is used for storing the interaction information; the master node and the worker node are also used for triggering the interactive master node or the worker node to inform the middleware of the interactive information when the computing engine actively triggers the event interaction; the function module is also used for acquiring the interaction information from the middleware.
In the embodiment of the application, a middleware module, such as a Message Queue (MQ) and the like, is added during deployment. In a scenario with a higher security level, such as a manufacturer of a bank or a government system, a message middleware self-developed by the manufacturer may be used. When the computing engine triggers active interaction, the interaction information can be stored in the middleware, and the data format stored in the middleware is used as a public document. When different manufacturers realize the functional modules, the corresponding interaction information can be obtained from the middleware, and after analysis, the functional modules can be used for subsequent functional logic realization. In the mode, a callback mechanism of a driver to the functional module is not needed, and the decoupling between the computing engine and the platform can be realized when the computing engine actively triggers the interaction. Wherein, different producers according to the standardization file that driver node provided and the standardization file of the data format of the middleware of relying on, the functional module of developer producer oneself accomplishes functional logic, and the functional module inside contains 2 partial functions: 1. the platform may invoke the functionality of the compute engine through the function module (the interaction is initiated actively by the platform). 2. When the computing engine actively interacts, the functional module acquires the data stored in the middleware, analyzes the data format, and then processes the corresponding interaction event (the computing engine actively initiates the interaction).
Similarly, after the functional module obtains the data stored in the middleware, the functional module performs an interaction action and obtains an interaction result, and due to the particularity of the middleware module, the interaction result is divided into 2 cases:
in the first case, under the condition that interaction does not need to return a result, the interaction result is returned to the driver node according to the function module, and then the driver node returns the interaction result to the master node and the worker node which trigger interaction.
The second case is that when the interaction requires a result to be returned, the functional module needs to transmit the result back to the middleware according to the specification of the middleware data format, and the calculation engine acquires the result from the middleware and then analyzes the data.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (12)
1. A method for decoupling a computing engine and a platform is characterized in that the method is applied to a plurality of platform sides participating in interaction, for each platform side, a functional module is arranged between a driver node and the platform of the computing engine, the functional module integrates service codes related to platform functions, and the computing engine further comprises a master node and a worker node;
the method comprises the following steps:
when a computing engine actively triggers event interaction, reporting interaction information by the master node or the worker node which triggers the interaction;
and processing the corresponding interaction behavior by the functional module according to the service code corresponding to the interaction information, and realizing the decoupling of the computing engine and the platform.
2. The method of claim 1, wherein the functional module is further configured to set a callback of a driver node;
before the functional module processes the corresponding interactive behavior according to the service code corresponding to the interactive information, the method further comprises the following steps:
the master node or the worker node which triggers interaction reports interaction information to a driver node;
receiving, by the driver node, the interaction information;
and calling the callback corresponding to the interaction of the functional module by the driver node according to the interaction information.
3. The method of claim 2, wherein the driver node is used to instruct a platform side to set a callback of the driver node by developing the functional module.
4. The method of claim 3, wherein the driver node provides a series of canonical interfaces that inform the platform side of the method and specification of setting callbacks in a public document.
5. The method of claim 4, prior to the compute engine actively triggering an event interaction, further:
for each platform side, developing a functional module corresponding to a platform service code based on a driver node;
and when the functional module is initialized, calling the callback setting method and the callback setting specification provided by the driver node, and setting the callback of the driver node.
6. The method of claim 1, wherein the functional modules further integrate the compute engine's acquisition registration algorithm, initiation task, and event communication functions.
7. The method of claim 1, comprising:
the master node is used for performing the functions of registering discovery, health detection, fault removal, fault recovery, system health and system alarm of computing resources, and is used for performing task load balancing scheduling of federal learning or multi-party safety computation, inter-node interaction events or routing distribution according to distribution events, so that the decoupling of the functional level is realized.
8. The method of claim 1, comprising:
when a computing engine is called to perform computing tasks, the function of a driver is called according to a developer document of a development kit, so that the function of the whole computing engine is called, a standard interface is defined by the driver, and the driver calls different platform parties, so that decoupling can be realized.
9. The method of claim 1, wherein before the functional module processes the corresponding interactive behavior according to the service code corresponding to the interactive information, the method further comprises:
when a computing engine actively triggers event interaction, a master node or a worker node which triggers the interaction reports interaction information;
receiving, by the middleware, the interaction information;
the functional module acquires the interaction information from the middleware so as to execute subsequent logic of interaction through the functional module and realize decoupling of the computing engine and the platform.
10. A system in which a compute engine is decoupled from a platform, comprising:
the master node and the worker node are used for reporting the interaction information by the master node or the worker node which triggers the interaction when the computing engine actively triggers the event interaction;
and the functional module integrates service codes related to platform functions, and is used for processing corresponding interaction behaviors according to the service codes corresponding to the interaction information so as to realize the decoupling of the computing engine and the platform.
11. The system of claim 10, further comprising:
and the driver node is used for receiving the interaction information reported by the master node or the worker node and calling a callback corresponding to interaction of the functional module according to the interaction information.
12. The system of claim 10, further comprising: the middleware is used for storing the interaction information;
the master node and the worker node are also used for triggering the interactive master node or the worker node to inform the middleware of the interactive information when the computing engine actively triggers the event interaction;
the function module is further configured to obtain the interaction information from the middleware.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210119038.5A CN114444136B (en) | 2022-02-08 | 2022-02-08 | Method and system for decoupling computing engine and platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210119038.5A CN114444136B (en) | 2022-02-08 | 2022-02-08 | Method and system for decoupling computing engine and platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114444136A true CN114444136A (en) | 2022-05-06 |
| CN114444136B CN114444136B (en) | 2024-08-30 |
Family
ID=81372533
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210119038.5A Active CN114444136B (en) | 2022-02-08 | 2022-02-08 | Method and system for decoupling computing engine and platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114444136B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114692207A (en) * | 2022-05-31 | 2022-07-01 | 蓝象智联(杭州)科技有限公司 | Data processing method and device for privacy protection and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101232626A (en) * | 2008-02-01 | 2008-07-30 | 中兴通讯股份有限公司 | Business supporting system and method based on business events developing platform |
| US20100325609A1 (en) * | 2009-06-17 | 2010-12-23 | Windley Phillip J | Rule engine system controlling devices of disparate types and protocols |
| CN103279840A (en) * | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN107911462A (en) * | 2017-11-27 | 2018-04-13 | 南京信通科技有限责任公司 | High-volume method of data synchronization based on ActiveMQ |
| CN112200505A (en) * | 2020-12-04 | 2021-01-08 | 望海康信(北京)科技股份公司 | Cross-business system process monitoring device and method, corresponding equipment and storage medium |
| CN112199087A (en) * | 2020-10-13 | 2021-01-08 | Oppo广东移动通信有限公司 | Configuration method, device, equipment and storage medium of application development environment |
| CN113505175A (en) * | 2021-07-08 | 2021-10-15 | 浪潮云信息技术股份公司 | Method for realizing MySQL incremental data synchronization based on message queue |
-
2022
- 2022-02-08 CN CN202210119038.5A patent/CN114444136B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101232626A (en) * | 2008-02-01 | 2008-07-30 | 中兴通讯股份有限公司 | Business supporting system and method based on business events developing platform |
| US20100325609A1 (en) * | 2009-06-17 | 2010-12-23 | Windley Phillip J | Rule engine system controlling devices of disparate types and protocols |
| CN103279840A (en) * | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN107911462A (en) * | 2017-11-27 | 2018-04-13 | 南京信通科技有限责任公司 | High-volume method of data synchronization based on ActiveMQ |
| CN112199087A (en) * | 2020-10-13 | 2021-01-08 | Oppo广东移动通信有限公司 | Configuration method, device, equipment and storage medium of application development environment |
| CN112200505A (en) * | 2020-12-04 | 2021-01-08 | 望海康信(北京)科技股份公司 | Cross-business system process monitoring device and method, corresponding equipment and storage medium |
| CN113505175A (en) * | 2021-07-08 | 2021-10-15 | 浪潮云信息技术股份公司 | Method for realizing MySQL incremental data synchronization based on message queue |
Non-Patent Citations (2)
| Title |
|---|
| AI浩: ""利用函数指针实现C的回调函数，实现调用者和底层驱动的解耦 第二种方式"", 《CSDN》 * |
| AI浩: ""利用函数指针实现C的回调函数，实现调用者和底层驱动的解耦 第二种方式"", 《CSDN》, 29 September 2020 (2020-09-29), pages 1 - 10 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114692207A (en) * | 2022-05-31 | 2022-07-01 | 蓝象智联(杭州)科技有限公司 | Data processing method and device for privacy protection and storage medium |
| CN114692207B (en) * | 2022-05-31 | 2022-09-20 | 蓝象智联(杭州)科技有限公司 | Data processing method and device for privacy protection and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114444136B (en) | 2024-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106375458B (en) | Service calling system, method and device | |
| CN110661662B (en) | Lightweight microservice configuration method | |
| CN110266815B (en) | Micro service network system based on block chain | |
| CN103812838A (en) | Service calling method and device and system | |
| CN113821363B (en) | Inter-process communication method and system | |
| CN111552568A (en) | Cloud service calling method and device | |
| CN102866925A (en) | Communication method and system for middleware and user interface | |
| CN114444136A (en) | Method and system for decoupling computing engine and platform | |
| CN111147600B (en) | Service execution method and terminal under cluster environment | |
| CN116366652A (en) | Distributed application operation and maintenance method, system, device, server and gateway equipment | |
| CN114926163A (en) | Resource cross-chain transfer method and device | |
| CN114840329A (en) | Cloud and native hybrid integration method based on block chain | |
| CN112799795B (en) | Service implementation method, process management method, device, equipment and storage medium | |
| CN110990015A (en) | Mobile software integration framework oriented to emergency command field and implementation method thereof | |
| CN110769378A (en) | Private network communication scheduling device, method and system | |
| CN115776501A (en) | Block chain system architecture, management method, electronic equipment and readable storage medium | |
| CN116389385A (en) | System resource processing method, device, storage medium and equipment | |
| CN114338584B (en) | Message withdraw method and message transmission system | |
| US20100061526A1 (en) | System, method and program product for triggering automatic transmission of emergency data during an emergency | |
| CN114338368A (en) | Network supervision method, equipment and medium based on unidirectional import equipment | |
| CN114296985A (en) | Global exception handling method and platform in large-scale micro-service cluster scene | |
| US10944658B2 (en) | Method, apparatus and system for method for start-up of monitoring of monitor objects in a computer-integrated telecommunications environment | |
| US20240264960A1 (en) | Managing a workspace mesh | |
| CN103368754A (en) | Service failure detection method, apparatus, system and device | |
| CN117472553B (en) | Workflow processing method, device, processing equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |