CN117112258A - Method for realizing data transmission between different services and related products - Google Patents
Method for realizing data transmission between different services and related products Download PDFInfo
- Publication number
- CN117112258A CN117112258A CN202311075931.3A CN202311075931A CN117112258A CN 117112258 A CN117112258 A CN 117112258A CN 202311075931 A CN202311075931 A CN 202311075931A CN 117112258 A CN117112258 A CN 117112258A
- Authority
- CN
- China
- Prior art keywords
- flow
- rule engine
- service
- expression
- interface
- 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
- 238000000034 method Methods 0.000 title claims abstract description 121
- 230000005540 biological transmission Effects 0.000 title claims abstract description 73
- 230000014509 gene expression Effects 0.000 claims abstract description 118
- 230000008569 process Effects 0.000 claims abstract description 77
- 238000004590 computer program Methods 0.000 claims description 10
- 238000011112 process operation Methods 0.000 claims description 4
- 238000012544 monitoring process Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 238000013461 design Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 238000013459 approach Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
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/54—Interprogram communication
- G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
-
- 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/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a method for realizing data transmission among different services and a related product, which can be applied to the technical field of computers, and the method comprises the following steps: establishing interface connection between a rule engine and non-flow service based on a user-defined flow expression in the flow operation process; based on the interface connection, data in the flow service is transferred to the non-flow service or the data in the non-flow service is sent to the flow service, so that data transmission among different services is realized. Therefore, the data transmission between the flow service and the non-flow service is realized by utilizing the self-defined flow expression language which is more in line with the programming habit of the developer, thereby improving the resource acquisition capability of the flow service and the flexibility of data acquisition.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method for implementing data transmission between different services and a related product.
Background
The flow expression language is used for setting flow conditions and node monitoring events in the flow design, and is a key that the flow can normally run.
The expression language supported by the current open-source flow engine is a simply set flow variable, and the local code implementation of the flow service is called. The prior art scheme cannot realize the resource acquisition of non-flow service, and cannot call a non-flow service interface to transmit data in a monitoring event. The data between different services are not communicated, and the problem of inflexible data acquisition exists.
Therefore, how to improve the flexibility of data acquisition is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
Based on the problems, the application provides a method for realizing data transmission among different services and related products, and the data transmission among the flow services and the non-flow services is realized by utilizing the custom flow expression language which is more in line with programming habits of developers, so that the resource acquisition capacity of the flow services is improved, and the problem of inflexible data acquisition in the prior art is solved.
In a first aspect, the present application provides a method for implementing data transmission between different services, including:
establishing interface connection between a rule engine and non-flow service based on a user-defined flow expression in the flow operation process;
based on the interface connection, data in the flow service is transferred to the non-flow service or the data in the non-flow service is sent to the flow service, so that data transmission among different services is realized.
Optionally, before establishing the interface connection between the rule engine and the non-flow service based on the custom flow expression during the flow operation, the method further includes:
adding an interface request method into a rule engine to develop the rule engine for the second time, so that the rule engine can carry out interface calling and dynamically acquire global flow variables in the process of flow operation.
Optionally, before establishing the interface connection between the rule engine and the non-flow service based on the custom flow expression during the flow operation, the method further includes:
and modifying the flow engine to enable the flow engine to support the custom rule engine grammar for calling the rule engine.
Optionally, in the process of running the flow, establishing an interface connection between the rule engine and the non-flow service based on the custom flow expression includes:
and in the running process of the flow, based on the secondarily developed rule engine, establishing interface connection between the rule engine and non-flow service by executing an interface calling expression in the grammar of the custom rule engine.
Optionally, before executing the interface call expression in the custom rule engine grammar, the method further includes:
inquiring all process variables involved in the process of running the process;
and automatically assigning the flow variable based on the variable of the declared variable name, and setting the assigned flow variable as the global parameter of the rule engine.
Optionally, in the process of running the flow, based on the rule engine developed secondarily, the interface connection between the rule engine and the non-flow service is established by executing the interface calling expression in the custom rule engine grammar, which includes:
reading an interface calling expression in the custom rule engine grammar in the process of running the flow;
automatically analyzing flow variables in the interface call expression based on the global parameters in the rule engine developed for the second time;
and executing the interface calling expression based on the parsed flow variable, and establishing interface connection between the rule engine and the non-flow service.
Optionally, based on the interface connection, the transferring the data in the flow service to the non-flow service or sending the data in the non-flow service to the flow service, to implement data transmission between different services, includes:
executing the custom flow expression;
when the custom flow expression contains a data transmission request to non-flow service, determining data to be transmitted by using the rule engine;
based on the interface connection, transmitting the data to be transmitted to the non-flow service by using the rule engine;
when the custom flow expression contains a data acquisition request from non-flow service, determining data to be acquired by utilizing the rule engine;
and based on the interface connection, the data to be transmitted is transferred to the non-flow service by using the rule engine.
In a second aspect, the present application provides an apparatus for implementing data transmission between different services, including:
the establishing module is used for establishing interface connection between the rule engine and the non-flow service based on the self-defined flow expression in the flow operation process;
and the transmission module is used for transmitting the data in the flow service to the non-flow service or transmitting the data in the non-flow service to the flow service based on the interface connection, so as to realize data transmission among different services.
In a third aspect, the present application provides an apparatus for implementing data transmission between different services, including:
a memory for storing a computer program;
a processor for implementing the steps of the method of implementing data transmission between different services as claimed in any one of the preceding claims when executing the computer program.
In a fourth aspect, the present application provides a readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of a method of enabling data transmission between different services as described in any of the preceding claims.
Compared with the prior art, the application has the following advantages that:
the method comprises the steps of firstly establishing interface connection between a rule engine and non-flow service based on a self-defined flow expression in the flow operation process. And then based on the interface connection, transmitting the data in the flow service to the non-flow service or transmitting the data in the non-flow service to the flow service, so as to realize data transmission among different services. Therefore, the data transmission between the flow service and the non-flow service is realized by utilizing the self-defined flow expression language which is more in line with the programming habit of the developer, thereby improving the resource acquisition capability of the flow service and the flexibility of data acquisition.
Drawings
FIG. 1 is a flow chart of a method for implementing data transmission between different services according to the present application;
FIG. 2 is a schematic timing diagram of a flow expression provided in the present application;
FIG. 3 is a schematic diagram of a trigger event and a circulation condition thereof according to the present application;
FIG. 4 is a schematic diagram of an interface call grammar provided by the present application;
fig. 5 is a schematic structural diagram of an apparatus for implementing data transmission between different services according to the present application.
Detailed Description
As described above, the existing technical solution has a problem that data acquisition is not flexible. Specifically, the flow expression language is used for setting circulation conditions and node monitoring events in the flow design. The expression language supported by the current open-source flow engine is simply set up flow variables, and the local code implementation of the flow service is called. The resource acquisition of the non-flow service cannot be realized, and the non-flow service interface cannot be called to transmit data in the monitoring event. For example, when the process and the service are respectively deployed by two services, only a simple process variable can be set in the monitoring event of the process design node or the event or a code implementation in the process service can be called. If the code realization of the service is to be called or the transmission of the flow data to the service flow is not completed, the existing technical scheme has inflexible problem on the aspect of data acquisition.
In order to solve the above problems, the present application provides a method for implementing data transmission between different services, including: firstly, in the process of running the flow, establishing interface connection between a rule engine and non-flow service based on a custom flow expression. And then based on the interface connection, transmitting the data in the flow service to the non-flow service or transmitting the data in the non-flow service to the flow service, so as to realize data transmission among different services.
Therefore, the data transmission between the flow service and the non-flow service is realized by utilizing the self-defined flow expression language which is more in line with the programming habit of the developer, thereby improving the resource acquisition capability of the flow service and the flexibility of data acquisition.
It should be noted that the method for realizing data transmission between different services and the related products provided by the application can be applied to the technical field of computers. The foregoing is merely exemplary, and the application fields of the method for implementing data transmission between different services and related products provided by the present application are not limited.
In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Fig. 1 is a flowchart of a method for implementing data transmission between different services according to the present application. Referring to fig. 1, a method for implementing data transmission between different services provided by the present application may include:
s101: during the process operation, the interface connection between the rule engine and the non-process service is established based on the custom process expression.
In practical application, the flow expression language is used for setting circulation conditions and node monitoring events in the flow design. The expression language supported by the current open-source flow engine is simply set up flow variables, and the local code implementation of the flow service is called. The resource acquisition of the non-flow service cannot be realized, and the non-flow service interface cannot be called to transmit data in the monitoring event. Therefore, the application provides a set of custom flow expression language which is more in line with programming habit of the developer, and the actions which the user wants to complete are more intuitively and efficiently realized. Taking the process service and the business service as examples, the interface connection between the process service and the business service, namely the interface connection with the non-process service, can be realized through the custom language expression. Specifically, there are a plurality of circulation conditions and node monitoring events formed by custom flow expressions in the whole flow, when the flow is operated to the custom expression, and the device for realizing data transmission between different services parses out that sentences for establishing interface connection between a rule engine and non-flow services exist in the expression, the interface connection between the rule engine and the flow services is realized by executing the expression.
In addition, the present application is described in terms of one possible implementation, as the functions that different rule engines can implement are not identical.
In one case, for development of the rule engine, correspondingly, before the interface connection between the rule engine and the non-flow service is established based on the custom flow expression during the flow operation, the method further includes:
adding an interface request method into a rule engine to develop the rule engine for the second time, so that the rule engine can carry out interface calling and dynamically acquire global flow variables in the process of flow operation.
In practical application, the rule engine is used to cooperate with the execution of the custom flow expression in the flow service. Since the custom flow expression is different from the conventional expression implemented by simply setting the flow variable and only calling the local code of the flow service, the rule engine needs to be secondarily developed by using a device for implementing data transmission between different services. In order to realize interface connection between the rule engine and the non-flow service, the application adds an interface request method into the rule engine, and puts interface execution logic into the rule engine, so that the rule engine can execute interface requests in the self-defined flow expression to construct interface connection between the non-flow service. The interface execution logic put into the rules engine is as follows:
expression creation/creation
ExpressRunner expressRunner＝new ExpressRunner()；
DefaultContext<String,Object>context＝new DefaultContext<String,Object>()；
Input interface request into expression resolution
context.put("cafFlow",cafFunctionWrapper)；
CafExpression.defaultContext＝context；
In addition, the secondarily developed rule engine can dynamically acquire global process variables during the process operation.
In addition, since the flow engines corresponding to different functional rule engines are different, the present application can be described with respect to one possible flow engine.
In one case, the flow engine is adapted for how the rule engine corresponds. Correspondingly, before establishing the interface connection between the rule engine and the non-flow service based on the custom flow expression in the flow operation process, the method further comprises the following steps:
and modifying the flow engine to enable the flow engine to support the custom rule engine grammar for calling the rule engine.
In practical application, the rule engine can perform interface call and dynamically acquire global flow variables in flow operation through secondary development. The flow engine to be used is also required to be modified so that it can support the rules engine grammar we package. Therefore, node monitoring can be directly programmed on line by using the custom flow expression in the flow design, and complex operations such as calling interfaces of non-flow engine services or acquiring flow variables in a flow engine are called. Specifically, the added flow engine expression language supports the custom flow expression in the scheme, so that the flow engine expression language automatically analyzes the expression when the circulation condition is executed. The method is edited in the process service and used with a rule engine after secondary development, and can realize the purpose of calling the custom expression of the non-process service interface, namely, the method for realizing the request of the definition expression interface is as follows:
in addition, since the manner of establishing the interface connection between the rule engine and the non-flow service is not the same, the present application can be described in terms of one possible establishment manner.
In one case, it is directed to how to establish an interface between the rules engine and the non-flow service. Accordingly, S101: in the process of flow operation, establishing interface connection between a rule engine and non-flow service based on a custom flow expression specifically comprises the following steps:
and in the running process of the flow, based on the secondarily developed rule engine, establishing interface connection between the rule engine and non-flow service by executing an interface calling expression in the grammar of the custom rule engine.
In practical application, the method is based on the modified flow engine and the secondarily developed rule engine. Fig. 2 is a timing diagram of a flow expression provided in the present application. In connection with the illustration of fig. 2, a user initiates a process, a process engine controls the start process, a rule engine obtains process variables from the process engine and executes a custom process expression, and the process engine feeds back a process initiation result. If there is an interface call expression in the custom expression, the interface call expression is executed, and then the non-flow service interface between the rule engine and the non-flow service is requested to be established, and the data transmission is realized and the execution result is returned through the interface.
In addition, since the ways of executing the interface call expressions are not identical, the present application can be described in terms of one possible implementation.
In practical applications, the expressions are called for how to execute the interfaces. Correspondingly, before executing the interface call expression in the custom rule engine grammar, the method further comprises:
inquiring all process variables involved in the process of running the process;
and automatically assigning the flow variable based on the variable of the declared variable name, and setting the assigned flow variable as the global parameter of the rule engine.
In practical application, the existing flow expression language needs to acquire the flow variable in a $ { flow variable } manner for acquiring the flow variable. This approach is not flexible and intuitive enough if multiple expressions are set. Therefore, before executing the interface call expression, the device for realizing data transmission among different services needs to query all the flow variables involved in the flow operation process and set as global parameters of the rule engine, and when executing the expression, the global parameters replace the variables in the expression. The purpose that the latest flow variable can be obtained when any node executes the expression is achieved. It should be noted that before setting the flow variable as the global parameter of the rule engine, automatic assignment needs to be performed on the flow variable, that is, the flow variable is automatically assigned based on the variable of the declared variable name. In the technical scheme provided by the application, only one variable of the flow variable name is required to be declared, and the flow variable in the flow operation can be automatically assigned by a device for realizing data transmission among different services. Fig. 3 is a schematic diagram of a trigger event and a circulation condition thereof according to the present application. In connection with the execution of the statement, automatic assignment of the flow variables is achieved, as shown in fig. 3. In addition, for the process variable to be transmitted into the rule engine, each process triggering event or the flow condition is transmitted into the context of the rule engine before being executed in the process of executing the process instance, and the process variable can be automatically analyzed in the process of executing the rule engine so as to achieve the purpose of acquiring the process variable. The expression and the specific analysis execution logic of the expression in the scheme are created in the flow engine as follows:
the flow runtime flow variables are expressed in the expression context as follows:
context.putAll(variable)；
expressRunner.execute(express,context,null,false,false)。
in addition, since the manner of establishing the interface connection between the rule engine and the non-flow service is not the same, the present application can be described in terms of one possible establishment manner.
In another case, it is directed to how to establish an interface between the rules engine and the non-flow service. Correspondingly, in the process of running the flow, based on the secondarily developed rule engine, the interface connection between the rule engine and the non-flow service is established by executing the interface calling expression in the grammar of the custom rule engine, which specifically comprises the following steps:
reading an interface calling expression in the custom rule engine grammar in the process of running the flow;
automatically analyzing flow variables in the interface call expression based on the global parameters in the rule engine developed for the second time;
and executing the interface calling expression based on the parsed flow variable, and establishing interface connection between the rule engine and the non-flow service.
In practical application, fig. 4 is a schematic diagram of an interface call grammar provided in the present application. In connection with the process shown in fig. 4, the data of the non-process service is obtained or transferred to the non-process service by adding the interface request method to the rule engine, and the interface call can be completed through the grammar shown in the figure. Specifically, in the process of running the flow, the device for realizing data transmission between different services reads the custom flow expression in the flow engine, and when the interface call expression in the grammar of the custom rule engine exists in the expression, the device automatically analyzes the flow variable in the interface call expression based on the flow variable which is queried before the execution of the expression in the rule engine developed for the second time and is set as the global parameter. Based on the parsed flow variables, executing an interface call expression, and establishing interface connection between the rule engine and the non-flow service.
S102: based on the interface connection, data in the flow service is transferred to the non-flow service or the data in the non-flow service is sent to the flow service, so that data transmission among different services is realized.
In practical application, the rule engine is developed secondarily so that the rule engine can carry out interface calling and dynamically acquire global flow variables in flow operation. And reforms the flow engine so that it can support our encapsulated rule engine syntax. Therefore, based on the interface connection, according to the data transmission request in the self-defined flow expression, the data in the flow service is transmitted to the non-flow service or the data in the non-flow service is transmitted to the flow service, so that the data transmission among different services is realized.
In addition, since the manner of data transmission based on the interface connection is not the same, the present application can be described with respect to one possible transmission manner.
In one case, it is directed to how data transfer is implemented based on the interfacing. Correspondingly, S102: based on the interface connection, transmitting data in a flow service to the non-flow service or transmitting data in the non-flow service to the flow service, so as to realize data transmission among different services, and specifically comprising the following steps:
executing the custom flow expression;
when the custom flow expression contains a data transmission request to non-flow service, determining data to be transmitted by using the rule engine;
based on the interface connection, transmitting the data to be transmitted to the non-flow service by using the rule engine;
when the custom flow expression contains a data acquisition request from non-flow service, determining data to be acquired by utilizing the rule engine;
and based on the interface connection, the data to be transmitted is transferred to the non-flow service by using the rule engine.
In practical application, the device for realizing data transmission between different services executes a custom flow expression, when an interface connection between a rule engine and a non-flow service exists in a flow and data in the flow service is transmitted to the non-flow service or the data in the non-flow service is transmitted to the custom flow expression in the flow service, the device for realizing data transmission between different services firstly builds the interface connection between the rule engine and the non-flow service when executing the custom flow expression, and then transmits the data in the flow service to the non-flow service or the data in the non-flow service to the flow service according to a request in the custom flow expression based on the interface connection, so that data transmission between different services is realized.
In summary, in the process of running the flow, the present application first establishes an interface connection between the rule engine and the non-flow service based on the custom flow expression. And then based on the interface connection, transmitting the data in the flow service to the non-flow service or transmitting the data in the non-flow service to the flow service, so as to realize data transmission among different services. Therefore, the data transmission between the flow service and the non-flow service is realized by utilizing the self-defined flow expression language which is more in line with the programming habit of the developer, thereby improving the resource acquisition capability of the flow service and the flexibility of data acquisition.
Based on the method for realizing data transmission between different services provided by the embodiment, the application also provides a device for realizing data transmission between different services. The apparatus for implementing data transmission between different services will be described with reference to the embodiments and the drawings, respectively.
Fig. 5 is a schematic structural diagram of an apparatus for implementing data transmission between different services according to an embodiment of the present application. Referring to fig. 5, an apparatus 200 for implementing data transmission between different services according to an embodiment of the present application includes:
the establishing module 201 is configured to establish an interface connection between the rule engine and the non-flow service based on the custom flow expression during the flow operation;
and the transfer module 202 is configured to transfer data in a flow service to the non-flow service or send data in the non-flow service to the flow service based on the interface connection, so as to implement data transmission between different services.
As an embodiment, the apparatus 200 for implementing data transmission between different services according to how to establish an interface connection between a rule engine and a non-flow service based on a custom flow expression further includes: developing a module;
and the development module is used for adding the interface request method into the rule engine to carry out secondary development on the rule engine, so that the rule engine can carry out interface calling and dynamically acquire global flow variables in the flow operation process.
As an embodiment, the apparatus 200 for implementing data transmission between different services according to how to establish an interface connection between a rule engine and a non-flow service based on a custom flow expression further includes: modifying the module;
and the transformation module is used for transforming the flow engine so that the flow engine can support the custom rule engine grammar for calling the rule engine.
As an embodiment, the above-mentioned establishing module 201 is specifically configured to establish an interface between a rule engine and a non-flow service based on a custom flow expression:
and in the running process of the flow, based on the secondarily developed rule engine, establishing interface connection between the rule engine and non-flow service by executing an interface calling expression in the grammar of the custom rule engine.
As an embodiment, the apparatus 200 for implementing data transmission between different services according to how to execute the interface call expression in the custom rule engine grammar further includes: a valuation module;
the assignment module is used for inquiring all the process variables involved in the process of the process operation;
and automatically assigning the flow variable based on the variable of the declared variable name, and setting the assigned flow variable as the global parameter of the rule engine.
As an embodiment, the above-mentioned building module 201 is specifically configured to, for how to execute the interface call expression in the custom rule engine grammar:
reading an interface calling expression in the custom rule engine grammar in the process of running the flow;
automatically analyzing flow variables in the interface call expression based on the global parameters in the rule engine developed for the second time;
and executing the interface calling expression based on the parsed flow variable, and establishing interface connection between the rule engine and the non-flow service.
As an embodiment, for how to transfer data in a flow service to a non-flow service or send data in a non-flow service to a flow service based on an interface connection, the transfer module 202 is specifically configured to:
executing the custom flow expression;
when the custom flow expression contains a data transmission request to non-flow service, determining data to be transmitted by using the rule engine;
based on the interface connection, transmitting the data to be transmitted to the non-flow service by using the rule engine;
when the custom flow expression contains a data acquisition request from non-flow service, determining data to be acquired by utilizing the rule engine;
and based on the interface connection, the data to be transmitted is transferred to the non-flow service by using the rule engine.
In summary, in the process of running the flow, the present application first establishes an interface connection between the rule engine and the non-flow service based on the custom flow expression. And then based on the interface connection, transmitting the data in the flow service to the non-flow service or transmitting the data in the non-flow service to the flow service, so as to realize data transmission among different services. Therefore, the data transmission between the flow service and the non-flow service is realized by utilizing the self-defined flow expression language which is more in line with the programming habit of the developer, thereby improving the resource acquisition capability of the flow service and the flexibility of data acquisition.
In addition, the application also provides a device for realizing data transmission among different services, comprising: a memory for storing a computer program; a processor for implementing the steps of the method of implementing data transmission between different services as claimed in any one of the preceding claims when executing the computer program.
In addition, the application also provides a readable storage medium, wherein the readable storage medium stores a computer program, and the computer program realizes the steps of the method for realizing data transmission between different services according to any one of the above steps when being executed by a processor.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for enabling data transmission between different services, the method comprising:
establishing interface connection between a rule engine and non-flow service based on a user-defined flow expression in the flow operation process;
based on the interface connection, data in the flow service is transferred to the non-flow service or the data in the non-flow service is sent to the flow service, so that data transmission among different services is realized.
2. The method of claim 1, wherein during the running of the process, before establishing the interface between the rule engine and the non-process service based on the custom process expression, further comprising:
adding an interface request method into a rule engine to develop the rule engine for the second time, so that the rule engine can carry out interface calling and dynamically acquire global flow variables in the process of flow operation.
3. The method of claim 2, wherein before establishing the interface between the rules engine and the non-process service based on the custom process expression during the running of the process, further comprising:
and modifying the flow engine to enable the flow engine to support the custom rule engine grammar for calling the rule engine.
4. The method of claim 3, wherein establishing an interface between the rules engine and the non-process service based on the custom process expression during the process operation comprises:
and in the running process of the flow, based on the secondarily developed rule engine, establishing interface connection between the rule engine and non-flow service by executing an interface calling expression in the grammar of the custom rule engine.
5. The method of claim 4, further comprising, prior to executing the interface call expression in the custom rules engine grammar:
inquiring all process variables involved in the process of running the process;
and automatically assigning the flow variable based on the variable of the declared variable name, and setting the assigned flow variable as the global parameter of the rule engine.
6. The method of claim 5, wherein establishing an interface between the rules engine and a non-flow service during flow operation by executing an interface call expression in the custom rules engine grammar based on the secondarily developed rules engine comprises:
reading an interface calling expression in the custom rule engine grammar in the process of running the flow;
automatically analyzing flow variables in the interface call expression based on the global parameters in the rule engine developed for the second time;
and executing the interface calling expression based on the parsed flow variable, and establishing interface connection between the rule engine and the non-flow service.
7. The method according to claim 1, wherein the transferring data in a flow service to the non-flow service or sending data in the non-flow service to the flow service based on the interface connection, to implement data transmission between different services, includes:
executing the custom flow expression;
when the custom flow expression contains a data transmission request to non-flow service, determining data to be transmitted by using the rule engine;
based on the interface connection, transmitting the data to be transmitted to the non-flow service by using the rule engine;
when the custom flow expression contains a data acquisition request from non-flow service, determining data to be acquired by utilizing the rule engine;
and based on the interface connection, the data to be transmitted is transferred to the non-flow service by using the rule engine.
8. An apparatus for enabling data transmission between different services, comprising:
the establishing module is used for establishing interface connection between the rule engine and the non-flow service based on the self-defined flow expression in the flow operation process;
and the transmission module is used for transmitting the data in the flow service to the non-flow service or transmitting the data in the non-flow service to the flow service based on the interface connection, so as to realize data transmission among different services.
9. An apparatus for enabling data transmission between different services, comprising:
a memory for storing a computer program;
a processor for carrying out the steps of the method for enabling data transmission between different services according to any of claims 1 to 7 when executing said computer program.
10. A readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a processor, implements the steps of the method of implementing data transmission between different services according to any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311075931.3A CN117112258A (en) | 2023-08-24 | 2023-08-24 | Method for realizing data transmission between different services and related products |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311075931.3A CN117112258A (en) | 2023-08-24 | 2023-08-24 | Method for realizing data transmission between different services and related products |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117112258A true CN117112258A (en) | 2023-11-24 |
Family
ID=88812303
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311075931.3A Pending CN117112258A (en) | 2023-08-24 | 2023-08-24 | Method for realizing data transmission between different services and related products |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117112258A (en) |
-
2023
- 2023-08-24 CN CN202311075931.3A patent/CN117112258A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11409949B2 (en) | Mobile device resource provisioning system and method | |
| Jespersen et al. | Session types for Rust | |
| US7451136B2 (en) | System and method for searching multiple disparate search engines | |
| CN110365751B (en) | Service processing method, device and equipment of gateway system | |
| CN108306844B (en) | Method for API communication between server and client | |
| CN112068970B (en) | RPC implementation method and medium based on heterogeneous multi-core processor | |
| US20240054366A1 (en) | AI Application Deployment Method and Related Platform, Cluster, Medium, and Program Product | |
| WO2024002299A1 (en) | Application management method, application subscription method, and related device | |
| CN110609755A (en) | Message processing method, device, equipment and medium for cross-block chain node | |
| CN108804100B (en) | Method and device for creating interface element, storage medium and mobile terminal | |
| US8458668B1 (en) | Ignoring output arguments of functions in programming environments | |
| EP1489504A2 (en) | Mechanism for asynchronous components to be application framework agnostic | |
| KR101286284B1 (en) | QoS-aware Web Service Composition method using On-the-fly Learning-based Search | |
| CN117112258A (en) | Method for realizing data transmission between different services and related products | |
| KR20100089831A (en) | Generation and management of managed javabean objects | |
| EP4044043A1 (en) | Storage process running method and apparatus, database system, and storage medium | |
| US9442782B2 (en) | Systems and methods of interface description language (IDL) compilers | |
| CN108008983B (en) | Multi-interface data processing method based on single process | |
| CN113918290A (en) | API calling method and device | |
| CN113760347A (en) | Data processing | |
| CN113220704B (en) | Method and device for deploying, querying and executing intelligent contracts in block chain | |
| WO2022166480A1 (en) | Task scheduling method, apparatus and system | |
| JP3007340B1 (en) | Function calling method, parallel distributed processing system and computer | |
| JPH11249919A (en) | Procedure call processing method and stub generation method | |
| CN109901826B (en) | Data processing method and device for Java program and electronic equipment |
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 |