WO2021093671A1 - Task processing method, system, apparatus and device, and computer readable storage medium - Google Patents

Abstract

A task processing method, system, apparatus and device based on platform interaction, and a computer readable storage medium, relating to the technical field of financial technology (Fintech). The method comprises: when an operation task is received, obtaining task information corresponding to the operation task (S10); determining, according to the task information, whether the operation task is to be transferred (S20); if the operation task is to be transferred, submitting the operation task to an external platform by means of a preset agent node so as to enable the external platform to process the operation task (S30); and receiving state information, fed back by the external platform, of the operation task, and performing state overturning on the operation task according to the state information till execution of the operation task is finished (S40).

Description

Task processing method, system, device, equipment and computer readable storage medium

This application claims the priority of the Chinese patent application filed on November 13, 2019, the application number is 201911110236.X, and the name is "task processing methods, systems, devices, equipment, and computer-readable storage media", all of which are Incorporated in this application by reference.

Technical field

This application relates to the field of financial technology (Fintech) technology, in particular to task processing methods, systems, devices, equipment and computer-readable storage media based on platform interaction.

Background technique

With the development of computer technology, more and more technologies are applied in the financial field. The traditional financial industry is gradually transforming to Fintech. The financial platform interactive technology is no exception, but due to the security and real-time requirements of the financial industry , But also higher requirements for technology.

The microservice platform has high concurrency, high performance, and high availability of big data operations, requests and other operational tasks full lifecycle management capabilities. The microservice platform is an open source system platform that can realize platform interaction by establishing a connection between the microservice platform and external platforms , To use the capabilities of the microservice platform to manage operational tasks. The interaction between the current microservice platform and external platforms is through RPC (Remote Procedure Call, remote procedure call) method, RPC method requires corresponding development on the microservice platform and the external platform, the development cost is higher, and the development coupling is higher, which reduces the willingness to access the external platform. How to reduce the degree of coupling between the microservice platform and the external platform, increase the willingness to access external platforms, and effectively utilize the capabilities of the microservice platform to achieve operational task management has become a technical problem that needs to be solved urgently.

Technical solutions

The main purpose of this application is to propose a task processing method, system, device, device, and computer-readable storage medium based on platform interaction, which aims to solve the current high coupling between microservice platforms and external platforms, which makes the willingness of external platforms to access Reduction, leading to the technical problem that the micro-service platform cannot be effectively used to achieve operational task management.

In order to achieve the above objective, this application provides a task processing method based on platform interaction. The task processing method based on platform interaction includes the following steps:

When an operation task is received, the task information corresponding to the operation task is acquired;

Judging whether to transfer the operation task according to the task information;

If the operation task is to be transferred, the operation task is submitted to an external platform through the preset agent node, so that the external platform can process the operation task;

The status information of the operation task fed back by the external platform is received, and the status of the operation task is flipped according to the status information until the execution of the operation task is completed.

In an embodiment, before the step of obtaining task information corresponding to the operation task when the operation task is received, the method includes:

When an external platform access request is received, access information corresponding to the external platform access request is obtained, where the access information includes a code for realizing interaction between the microservice platform and the external platform;

Compiling the code in the access information to form a jar package, and adding the jar package to the plug-in directory of the microservice platform;

Upon receiving the microservice startup request, query the plug-in directory to load the jar package to form a preset proxy node.

In an embodiment, the step of judging whether to transfer the operation task according to the task information includes:

Extracting the first task identifier in the task information, and determining the task type corresponding to the first task identifier;

If the task type corresponding to the first task identifier is a microservice task type, it is determined not to transfer the operation task;

If the task type corresponding to the first task identifier is an agent task type, it is determined that the operation task is to be transferred.

In an embodiment, the step of receiving the status information of the operation task fed back by the external platform, and flipping the status of the operation task according to the status information until the execution of the operation task is completed includes:

Receiving a second task identifier set by the external platform for the operation task, encapsulating the second task identifier, and generating an acquisition request including the second task identifier;

The acquisition request is sent to an external platform through the preset proxy node, so that the external platform locates the operation task according to the second task identifier in the acquisition request, and obtains the log corresponding to the operation task, or status information;

Receive the log or status information corresponding to the acquisition request that the external platform feeds back to the preset agent node, and adjust the status of the operation task according to the log or the status information until the execution of the operation task is completed.

In an embodiment, the step of receiving the status information of the operation task fed back by the external platform, and flipping the status of the operation task according to the status information until the execution of the operation task is completed includes:

Receive the second task identifier of the operation task fed back by the external platform, and generate an asynchronous response instance corresponding to the second task identifier, wherein a listener is set in the asynchronous response instance, and a callback method is set in the listener ；

When the asynchronous response instance monitors the trigger event of the operation task corresponding to the second task identifier, the callback method is executed and the state of the operation task is adjusted according to the trigger event until the execution of the operation task is completed.

In an embodiment, the step of receiving the status information of the operation task fed back by the external platform, and turning the status of the operation task according to the status information until after the execution of the operation task is completed, includes:

When it is detected that the execution of the operation task is completed, the execution result information of the operation task is fed back to the user terminal, and the resources of the operation task are released.

In an embodiment, the task processing method based on platform interaction further includes:

When receiving the offline request of the external platform, obtain the platform ID corresponding to the offline request of the external platform;

Query the plug-in directory of the microservice platform, obtain the jar package corresponding to the platform identifier, delete the jar package, and offline the external platform corresponding to the platform identifier.

In addition, in order to achieve the above objective, the present application also provides a task processing system based on platform interaction. The task processing system based on platform interaction includes: a microservice platform and an external platform connected in communication, the microservice platform and the The external platform interaction implements the following steps:

When the microservice platform receives the operation task, the microservice platform obtains the task information corresponding to the operation task;

The microservice platform judges whether to transfer the operation task according to the task information;

If the operation task is to be transferred, the microservice platform submits the operation task to an external platform through the preset agent node, so that the external platform can process the operation task;

The external platform executes the operation task to generate the log or status information corresponding to the operation task, and the external platform calls the network interface of the microservice platform to feed back the log or the status information;

When the microservice platform detects that the network interface is called, the microservice platform obtains the log or the status information fed back by the network interface;

The microservice platform performs state inversion of the operation task according to the log or the status information until the execution of the operation task is completed.

In addition, in order to achieve the above objective, the present application also provides a task processing device based on platform interaction.

In addition, in order to achieve the above objective, this application also provides a task processing device based on platform interaction. The task processing device based on platform interaction includes: a memory, a processor, and a A task processing program based on platform interaction running on the platform, and when the task processing program based on platform interaction is executed by the processor, the steps of the task processing method based on platform interaction as described above are implemented.

In addition, in order to achieve the above object, the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a task processing program based on platform interaction, and the task processing program based on platform interaction is executed by a processor. When realizing the steps of the task processing method based on platform interaction as described above.

In the embodiment of this application, the interaction between the microservice platform and the external platform is realized through the preset proxy node. Developers do not need to carry out corresponding development on the microservice platform and the external platform, which reduces the development cost and development coupling degree, and improves the external The willingness of platform access to effectively utilize the capabilities of the microservice platform to achieve operational task management.

Description of the drawings

FIG. 1 is a schematic diagram of a device structure of a hardware operating environment involved in a solution of an embodiment of the present application;

2 is a schematic flowchart of a first embodiment of a task processing method based on platform interaction according to this application;

3 is a schematic diagram of a specific scenario in the first embodiment of a task processing method based on platform interaction according to this application;

4 is a schematic flowchart of a second embodiment of a task processing method based on platform interaction according to this application;

5 is a schematic flowchart of a third embodiment of a task processing method based on platform interaction according to this application;

6 is a schematic diagram of a specific scenario of an embodiment of a task processing system based on platform interaction according to this application;

FIG. 7 is a schematic diagram of functional modules of an embodiment of a task processing apparatus based on platform interaction according to this application.

Embodiments of the present invention

It should be understood that the specific embodiments described here are only used to explain the application, and not used to limit the application.

As shown in FIG. 1, FIG. 1 is a schematic diagram of the device structure of the hardware operating environment involved in the solution of the embodiment of the present application.

The task processing device based on platform interaction in the embodiment of the present application may be a terminal or a server. As shown in FIG. 1, the task processing device based on platform interaction may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, and a memory 1005, communication bus 1002. Among them, the communication bus 1002 is used to implement connection and communication between these components. The user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as disk storage. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

Those skilled in the art can understand that the structure of the device shown in FIG. 1 does not constitute a limitation on the device, and may include more or fewer components than those shown in the figure, or a combination of certain components, or different component arrangements.

As shown in FIG. 1, the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a task processing program based on platform interaction.

In the device shown in Figure 1, the network interface 1004 is mainly used to connect to the back-end server and communicate with the back-end server; the user interface 1003 is mainly used to connect to the client (user side) to communicate with the client; and the processor 1001 can be used to call a task processing program based on platform interaction stored in the memory 1005, and perform operations in the following task processing method based on platform interaction.

In the prior art, the interaction between the microservice platform and the external platform uses RPC (Remote Procedure Call, remote procedure call) method, RPC is an inter-process communication method, RPC allows the program to call another address space (usually on another machine sharing the network) procedures or functions, without the programmer's explicit coding The details of this remote call. That is, whether the programmer calls the local or remote, the calling code written is basically the same. The application of such platform interaction methods in distributed systems is extremely wide, but there are still some shortcomings. For example, when the microservice platform is an open source project Linkis system platform, the following types of problems arise:

1) Both parties of the current platform interaction RPC method need to develop correspondingly on their own platforms, and the degree of development coupling is relatively high. If you want to develop a set of RPC, the development cost of the Linkis system platform and the external platform is higher, and the willingness to access the external platform will be reduced.

2) The RPC access scheme is embedded and does not have the characteristics of plug-in development. Since the use of the existing RPC framework on the market will cause the linkis system platform and external platforms to introduce more dependencies, the code cleanliness of the linkis system platform and external platforms cannot be maintained.

3) The deployment of the RPC method is more complicated. The RPC method requires the deployment of several basic services, such as service registration and discovery centers, which is not conducive to agile development.

Based on the foregoing hardware structure and platform interaction issues, an embodiment of the task processing method based on platform interaction in this application is proposed.

The first embodiment of the task processing method based on platform interaction of this application includes:

When an operation task is received, the task information corresponding to the operation task is acquired;

Judging whether to transfer the operation task according to the task information;

If the operation task is to be transferred, the operation task is submitted to an external platform through the preset agent node, so that the external platform can process the operation task;

The status information of the operation task fed back by the external platform is received, and the status of the operation task is flipped according to the status information until the execution of the operation task is completed.

The task processing method in this embodiment is applied to task processing equipment in financial institutions (banking institutions, insurance institutions, securities institutions, etc.) in the financial industry. The task processing equipment is the hardware carrier of the task processing platform. The tasks in this embodiment The processing platform can be set on the microservice platform. In addition, the task processing platform in this embodiment can also be used as an intermediate platform to connect the microservice platform and the external platform.

The microservice platform involved in this embodiment refers to a big data middleware platform developed by the financial industry. The microservice platform integrates multiple computing storage engines, such as Spark, TiSpark, Hive, Python, and HBase, for external provision Unified REST/WebSocket/JDBC interface, submit data middleware that executes SQL, Pyspark, HiveQL, Scala and other scripts. For example, the microservice platform is the Linkis system platform (The Linkis system platform is based on the microservice architecture and provides financial-level multi-tenant isolation, resource management and control, authority isolation and other enterprise-level features, and supports unified variable, UDF, function, and user resource file management. With high concurrency, high performance, high availability big data job/request full life cycle management capabilities).

The external platform involved in this embodiment is a platform with functions other than the microservice platform function. For example, the microservice platform is the Linkis system platform, and the Linkis system platform supports many internal execution engines, such as spark, hive, python, Hbase, etc. , But the Linkis system platform does not have the mail sending function, quality inspection function, the external platform can be the mail system platform, data quality inspection platform and so on.

In order to facilitate understanding, this embodiment takes the task processing platform set on the microservice platform as an example for description. In this embodiment, the agent node of the external platform is set in the microservice platform in advance, and the microservice platform and the microservice platform are implemented through the agent node. The interaction between external platforms, specifically, includes:

When an external platform access request is received, access information corresponding to the external platform access request is obtained, where the access information includes a code for realizing interaction between the microservice platform and the external platform;

Compiling the code in the access information to form a jar package, and adding the jar package to the plug-in directory of the microservice platform;

Upon receiving the microservice startup request, query the plug-in directory to load the jar package to form a preset proxy node.

That is, in this embodiment, the micro service platform receives the external platform access request, the micro service platform obtains the access information corresponding to the external platform access request, and the access information contains the code for realizing the interaction between the micro service platform and the external platform; The service platform compiles the code in the access information to form a jar package, that is, the microservice platform compiles the code in the access information into a binary language that can be recognized by the computer, and the microservice platform encapsulates the compiled information to form a jar package. The service platform adds the jar package to the plug-in directory of the microservice platform according to the specified naming rules; the microservice platform starts the microservice to initialize, and generates the proxy node corresponding to the external platform to interact with the platform through the proxy node, that is, the microservice platform When receiving the microservice startup request, query the plug-in directory to load the jar package to form a preset proxy node corresponding to the external platform, so as to provide services through the preset proxy node.

In this embodiment, the external platform connects to the microservice platform in the form of plug-ins. The external platform only needs to implement the necessary interfaces and place the implemented jar package in the plug-in directory specified by the microservice platform to interact with the microservice platform. ; In this embodiment, the external platform access cost is low, and the external platform and the microservice platform are in a low-coupling state. The external platform developers want to access the microservice platform, and there is almost no need to modify the native code of the external platform. The service platform is completely decoupled.

For example, the microservice platform is the Linkis system platform, and the external platform wants to interact with the Linkis system platform. First, after compiling and packaging the interactive code into a jar package, it is placed in the AppJointEntrance (application joint interface) plug-in of the Linkis system platform according to the naming convention. Under the directory, after the AppJointEntrance microservice in the Linkis system platform is started, it will go to the plugin directory to load the jar package to form AppJoint to provide the service.

It is understandable that AppJoint is a top-level abstract interface. AppJoint provides the interface methods needed for the Linkis system platform and external platforms to interact. AppJoint has functions such as submitting execution, querying task status, querying task logs, and killing tasks. An external platform (such as a data quality inspection platform) wants to interact with the microservice platform, and the way of interaction is determined by the external platform itself.

Compared with the RPC method, the access method of AppJoint in this embodiment has the following advantages: 1. There is no need to perform specific development on the microservice platform and external platform at the same time, 2. The deployment method is simple; Compared with the direct use of HTTP, the access method has the following advantages: unified interfaces; 2. Do not implement strong binding between interfaces and specific services to facilitate horizontal expansion.

The concept of AppJoint is not only applicable to the Linkis system. For other microservice platforms that wish to access multiple external platforms and obtain the execution capabilities of these external platforms, AppJoint is also a good way. AppJoint can act like a joint. , To connect different platforms, and coordinate different platforms to work, just like a person's elbow joint, connect the person's upper arm and lower arm and coordinate the movement of the two. The introduction of Appjoint allows a microservice system to access a variety of external platforms, and to interact with these external platforms in a unified way. Realize the decoupling between different platforms.

Further, after the establishment of the preset agent node, the microservice platform can submit the operation task submitted by the user to the external platform for execution, and obtain the information generated by the operation of the operation task on the external platform, so as to realize the management of the operation task, specifically:

Referring to Fig. 2, Fig. 2 is a schematic flowchart of a first embodiment of a task processing method based on platform interaction according to this application. The method includes:

Step S10, when an operation task is received, task information corresponding to the operation task is obtained;

The microservice platform receives operation tasks, and the triggering method of operation tasks is not specifically limited, that is, operation tasks can be triggered actively, for example, the customer clicks "Business Management" on the terminal to actively trigger the operation task; in addition, the operation task can also be automatic Triggered, for example, the micro-service platform presets the operation task of performing data update every day in the early morning, and the micro-service platform automatically triggers the operation task of data update when it arrives in the early morning.

When the microservice platform receives an operation task, the microservice platform obtains task information corresponding to the operation task, where the task information includes task identification and task execution information.

Step S20, judging whether to transfer the operation task according to the task information.

The task types of the operation tasks in this embodiment are various. For example, the task types include the spark hive and other micro-service task types supported by the micro-service platform, as well as the agent task types that the micro-service platform does not support, such as data quality inspection. Operation task, operation task of mail sending, etc. The microservice platform needs to determine whether to transfer the operation task according to the task information of the operation task.

For example, in conjunction with Figure 3, the microservice platform is the Linkis system platform, and the Linkis system platform is set with LinkisGateway. The LinkisGateway recognizes the task identifier and determines whether to forward the operation task. For example, the specified parameters are preset in the LinkisGateway, if the task of the operation task is If the identifier contains the specified parameter, the microservice platform will keep the operation task in itself for execution; if the task identifier of the operation task does not contain the specified parameter, then the operation task will be forwarded by LinkisGateway to the corresponding preset agent node.

This embodiment provides a specific implementation method for judging whether to transfer an operation task based on task information, including:

Step a1, extract the first task identifier in the task information, and determine the task type corresponding to the first task identifier;

Step a2, if the task type corresponding to the first task identifier is a microservice task type, it is determined not to transfer the operation task;

Step a3: If the task type corresponding to the first task identifier is an agent task type, it is determined that the operation task is to be transferred.

That is, the microservice platform extracts the first task identifier in the task information, and the microservice platform determines the task type corresponding to the first task identifier; that is, the task identifier and task type mapping table is preset in the microservice platform, and the microservice platform queries the mapping table , Obtain the task type corresponding to the first task identifier. If the task type corresponding to the first task identifier is a microservice task type, the microservice platform retains the operation task for execution; if the task type corresponding to the first task identifier is an agent task Type, the micro-service platform submits the operation task to the preset agent node.

In step S30, if the operation task is to be transferred, the operation task is submitted to an external platform through the preset agent node, so that the external platform can process the operation task.

If the operation task is submitted to the preset agent node, the microservice platform submits the operation task to the external platform through the preset agent node, so that the external platform can process the operation task; in this embodiment, the microservice platform Connect with external platforms, and coordinate the work of the micro-service platform and external platforms.

Step S40: Receive state information of the operation task fed back by the external platform, and perform state inversion of the operation task according to the state information until the execution of the operation task is completed.

The microservice platform receives the status information of the operation task fed back by the external platform. The status information includes: initialization status, waiting scheduling status, running status, failure status or success status; the microservice platform flips the status of the operation task according to the status information until the operation task The execution is completed to realize the management of operational tasks.

In this embodiment, the interaction between the microservice platform and the external platform is realized through the preset agent node, and the developer does not need to carry out corresponding development on the microservice platform and the external platform, which reduces the development cost and development coupling degree, and improves the external platform Willingness to access to effectively utilize the capabilities of the microservice platform to achieve operational task management.

After step S40 in this embodiment, it includes: when the microservice platform detects that the execution of the operation task is completed, the microservice platform feeds back the execution result information of the operation task to the user terminal that sends the operation task, and releases the resource of the operation task.

Further, based on the first embodiment of the task processing method based on platform interaction of the present application, the second embodiment of the task processing method based on platform interaction of the present application is proposed.

Referring to Figure 4, this embodiment is a refinement of step S30 in the first embodiment. This embodiment specifically describes the way to update the status of the operation task in a synchronous manner to realize the management of the operation task, including:

Step S31: Receive a second task identifier set by the external platform for the operation task, encapsulate the second task identifier, and generate an acquisition request containing the second task identifier.

The preset agent node in the microservice platform receives the second task identifier set by the external platform for the operation task, and the microservice platform encapsulates the second task identifier, and generates an acquisition request containing the second task identifier.

Step S32: Send the acquisition request to an external platform through the preset proxy node, so that the external platform locates the operation task according to the second task identifier in the acquisition request, and obtains the corresponding operation task Log or status information.

The microservice platform sends the acquisition request carrying the second task identifier to the external platform through the preset agent node, so that the external platform locates the operation task according to the second task identifier in the acquisition request, and the external platform determines the operation task corresponding to the second task identifier , The external platform obtains the log or status information corresponding to the operation task, and sends the log or status information to the preset agent node of the microservice platform.

Step S33: Receive the log or status information corresponding to the acquisition request that the external platform feeds back to the preset agent node, and adjust the status of the operation task according to the log or the status information until the operation task The execution is complete.

The microservice platform receives the log or status information corresponding to the acquisition request that the external platform feeds back to the preset agent node, and the microservice platform adjusts the status of the operation task according to the log or status information until the execution of the operation task is completed.

That is, the preset agent node in the microservice platform sends the operation task in the form of HTTP request to the external platform, and the external platform obtains the operation task in the manner of HTTP request. The external platform sets the second task flag for the operation task, and sets the second task The mark is fed back to the preset agent node in the microservice platform. The microservice platform encapsulates the second task mark into a request body (for example, Action). Every time the task thread is running in the future, the preset agent node will Carry the above action into the acquisition request to request an external platform. After the external platform receives the acquisition request, it will locate the operation task according to the content in the action, and obtain the log or status information of the operation task. If the log or status information of the operation task is obtained, the external platform will return the log to the appjoint. For the status information of the operation task, the external platform returns the status information to the appjoint, and the microservice platform adjusts the status of the operation task according to the log or status information until the execution of the operation task is completed.

In this embodiment, the preset agent node sends operation tasks in the form of HTTP requests, and the task information corresponding to the operation tasks is directly invoked by HTTP, and does not require interface design and specific services to achieve strong binding, which is convenient for external platforms Horizontal expansion.

Further, based on the foregoing embodiments of the task processing method based on platform interaction of the present application, a third embodiment of the task processing method based on platform interaction of the present application is proposed.

Referring to Figure 5, this embodiment is a refinement of step S30 in the first embodiment. This embodiment specifically illustrates the way of performing operation task status update asynchronously to realize operation task management, including:

Step S34: Receive the second task identifier of the operation task fed back by the external platform, and generate an asynchronous response instance corresponding to the second task identifier, wherein a listener is set in the asynchronous response instance, and the listener is Set the callback method.

The microservice platform receives the second task identifier of the operation task fed back by the external platform, and the microservice platform generates an asynchronous response instance corresponding to the second task identifier, wherein a listener is set in the asynchronous response instance, and a callback method is set in the listener .

Step S35: When the asynchronous response instance monitors the trigger event of the operation task corresponding to the second task identifier, execute the callback method and adjust the state of the operation task according to the trigger event until the operation task is executed carry out.

The microservice platform monitors the operation task corresponding to the second task identifier through the asynchronous response instance. When the trigger event of the operation task corresponding to the second task identifier is monitored, the microservice platform executes the callback method and adjusts the operation task according to the actual information of the trigger event. Status until the completion of the operation task execution.

That is, when an operation task is executed on an external platform, there will be task status flips, and task logs will also be generated. Once the task information is generated, the external platform will package and encapsulate the data and send it to the microservice platform designated for A restful interface for asynchronous callbacks. After the restful interface is called, the microservice platform will manage the operation task. The microservice platform will find the operation task according to the second task table of the task carried in the restful interface. If the request carries information such as state flip or log, the listener in the corresponding task will call the set callback method. The callback method includes the state reversal of the task in the microservice platform, the subsequent operations after the task reversal (such as persisting to data, etc.), and the writing of the log to the directory managed by the microservice platform.

The communication protocol in this embodiment is simple to implement and deploy using HTTP. At the same time, the listener mode is used to implement the callback of the task when the status information changes. The callback method is performed in the HTTP mode, and a url (url) is set for each operation task. The design can be composed of ${prefix prefix}/${task id}/callback callback, so that after the external platform calls the url, the microservice platform can directly know the task ID that the external platform wants to update, and then find it through the task ID The operation task, update the task), the external platform only needs to request this url to achieve asynchronous return. After the task is executed by the external system, the external platform returns an asynchronous response and returns the generated information to the microservice platform , To achieve convenient asynchronous communication between the two platforms.

Further, based on the foregoing embodiment of the task processing method based on platform interaction of the present application, a fourth embodiment of the task processing method based on platform interaction of the present application is proposed.

This embodiment can be combined with any of the other embodiments. In this embodiment, the microservice platform can offline some external platforms, including:

When receiving the offline request of the external platform, obtain the platform ID corresponding to the offline request of the external platform;

Query the plug-in directory of the microservice platform, obtain the jar package corresponding to the platform identifier, delete the jar package, and offline the external platform corresponding to the platform identifier.

In this embodiment, when the microservice platform receives an external platform offline request, the microservice platform obtains the platform identifier corresponding to the external platform offline request; the microservice platform queries its own plug-in catalog, and the microservice platform obtains the jar package corresponding to the platform identifier. Delete the jar package for the microservice platform, and identify the external platform corresponding to the offline platform. In this embodiment, the micro-service platform can offline the external platform by deleting the jar package, which realizes the hot-plugging of the external platform. The offline of the external platform will not affect the micro-service platform or interact with the micro-service platform. Other operating platforms.

An embodiment of the present application also provides a task processing system based on platform interaction. The task processing device based on platform interaction includes: a microservice platform and an external platform that are communicatively connected. The interaction between the microservice platform and the external platform realizes the following step:

When the microservice platform receives the operation task, the microservice platform obtains the task information corresponding to the operation task;

The microservice platform judges whether to transfer the operation task according to the task information;

If the operation task is to be transferred, the microservice platform submits the operation task to an external platform through the preset agent node, so that the external platform can process the operation task;

The external platform executes the operation task to generate the log or status information corresponding to the operation task, and the external platform calls the network interface of the microservice platform to feed back the log or the status information;

When the microservice platform detects that the network interface is called, the microservice platform obtains the log or the status information fed back by the network interface;

The microservice platform performs state inversion of the operation task according to the log or the status information until the execution of the operation task is completed.

6, in this embodiment, a user submits a task to the microservice platform. When the microservice platform receives an operation task, the microservice platform obtains task information corresponding to the operation task. The microservice platform determines the microservice platform based on the task information. The operation task is not supported and needs to be performed with the help of an external platform. The microservice platform submits the operation task to the preset agent node, and the operation task is submitted to the external platform through the preset agent node, so that the external platform can process the operation task.

After the external platform receives the request, the external platform repackages the operation task into a task that it can perform. After the task is generated, the external platform returns a response to the microservice platform. After the default proxy node in the microservice platform receives this response, it will generate an asynchronous response instance, in which a listener will be set, and the callback method will be set in the listener. Once the event that triggers it is monitored, it will be executed. The callback method is used to call the network interface of the microservice platform to feed back the log or status information of the operation task.

When the microservice platform detects that the network interface is called, the microservice platform obtains the log or the status information fed back by the network interface; the microservice platform reverses the status of the operation task according to the log or status information until the execution of the operation task is completed.

For the method executed by the task processing system based on platform interaction, please refer to the various embodiments of the task processing method based on platform interaction in this application, which will not be repeated here.

Referring to FIG. 7, an embodiment of the present application also provides a task processing device based on platform interaction, and the task processing device based on platform interaction includes:

The request receiving module 10 is configured to obtain task information corresponding to the operation task when the operation task is received;

The transfer judgment module 20 is configured to judge whether to transfer the operation task according to the task information;

The task forwarding module 30 is configured to, if the operation task is to be transferred, submit the operation task to an external platform through the preset agent node, so that the external platform can process the operation task;

The receiving and turning module 40 is configured to receive the state information of the operation task fed back by the external platform, and perform state inversion of the operation task according to the state information until the execution of the operation task is completed.

In an embodiment, the task processing device based on platform interaction includes:

The information acquisition module is used to acquire the access information corresponding to the external platform access request when the external platform access request is received, wherein the access information contains the code for realizing the interaction between the microservice platform and the external platform;

The information insertion module is used to compile the code in the access information to form a jar package, and add the jar package to the plug-in directory of the microservice platform;

The load generation module is used to query the plug-in directory to load the jar package when receiving the microservice startup request to form a preset proxy node.

In an embodiment, the transfer judgment module 20 includes:

An identification extraction unit, configured to extract the first task identification in the task information, and determine the task type corresponding to the first task identification;

A first determining unit, configured to determine not to transfer the operation task if the task type corresponding to the first task identifier is a microservice task type;

The second determining unit is configured to determine that the operation task is to be transferred if the task type corresponding to the first task identifier is an agent task type.

In an embodiment, the receiving and turning module 40 includes:

A receiving and generating unit, configured to receive a second task identifier set by the external platform for the operation task, encapsulate the second task identifier, and generate an acquisition request including the second task identifier;

The request sending unit is configured to send the acquisition request to an external platform through the preset proxy node, so that the external platform locates the operation task according to the second task identifier in the acquisition request, and acquires the Log or status information corresponding to the operation task;

The receiving adjustment unit is configured to receive the log or status information corresponding to the acquisition request that the external platform feeds back to the preset agent node, and adjust the status of the operation task according to the log or the status information, until all The execution of the operation task is completed.

In an embodiment, the receiving and turning module 40 includes:

The receiving and generating unit is configured to receive the second task identifier of the operation task fed back by the external platform, and generate an asynchronous response instance corresponding to the second task identifier, wherein a listener is set in the asynchronous response instance, and the Set the callback method in the listener;

The callback flipping unit is configured to execute the callback method and adjust the state of the operation task according to the trigger event when the asynchronous response instance monitors the trigger event of the operation task corresponding to the second task identifier, until the The operation task is completed.

In an embodiment, the task processing device based on platform interaction includes:

The resource release module is configured to, when the completion of the execution of the operation task is detected, feedback the execution result information of the operation task to the user terminal, and release the resources of the operation task.

In an embodiment, the task processing device based on platform interaction includes:

The offline request module is used to obtain the platform ID corresponding to the offline request of the external platform when the offline request of the external platform is received;

The platform offline module is used to query the plug-in directory of the microservice platform, obtain the jar package corresponding to the platform identifier, delete the jar package, and offline the external platform corresponding to the platform identifier.

For the methods executed by the above-mentioned program modules, please refer to the various embodiments of the task processing method based on platform interaction in this application, which will not be repeated here.

The application also provides a computer-readable storage medium.

The computer-readable storage medium of the present application stores a task processing program based on platform interaction, and when the task processing program based on platform interaction is executed by a processor, the steps of the task processing method based on platform interaction as described above are realized.

For the method implemented when the task processing program based on platform interaction running on the processor is executed, please refer to the various embodiments of the task processing method based on platform interaction of this application, which will not be repeated here.

It should be noted that in this article, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements not only includes those elements, It also includes other elements not explicitly listed, or elements inherent to the process, method, article, or system. Without more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or system that includes the element.

The serial numbers of the foregoing embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM) as described above. , Magnetic disks, optical disks), including several instructions to make a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the method described in each embodiment of the present application.

The above are only the preferred embodiments of the application, and do not limit the scope of the patent for this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of the application, or directly or indirectly applied to other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims (11)

1. A task processing method based on platform interaction, wherein the task processing method based on platform interaction includes the following steps:

   When an operation task is received, the task information corresponding to the operation task is acquired;

   Judging whether to transfer the operation task according to the task information;

   If the operation task is to be transferred, the operation task is submitted to an external platform through the preset agent node, so that the external platform can process the operation task;

   The status information of the operation task fed back by the external platform is received, and the status of the operation task is flipped according to the status information until the execution of the operation task is completed.
2. The task processing method based on platform interaction according to claim 1, wherein, before the step of obtaining task information corresponding to the operation task when the operation task is received, the method comprises:

   When an external platform access request is received, access information corresponding to the external platform access request is obtained, where the access information includes a code for realizing interaction between the microservice platform and the external platform;

   Compiling the code in the access information to form a jar package, and adding the jar package to the plug-in directory of the microservice platform;

   Upon receiving the microservice startup request, query the plug-in directory to load the jar package to form a preset proxy node.
3. The task processing method based on platform interaction according to claim 1, wherein the step of judging whether to transfer the operation task according to the task information comprises:

   Extracting the first task identifier in the task information, and determining the task type corresponding to the first task identifier;

   If the task type corresponding to the first task identifier is a microservice task type, it is determined not to transfer the operation task;

   If the task type corresponding to the first task identifier is an agent task type, it is determined that the operation task is to be transferred.
4. The task processing method based on platform interaction according to claim 1, wherein the state information of the operation task fed back by the external platform is received, and the state of the operation task is flipped according to the state information until the The steps to complete the execution of the operation task include:

   Receiving a second task identifier set by the external platform for the operation task, encapsulating the second task identifier, and generating an acquisition request including the second task identifier;

   The acquisition request is sent to an external platform through the preset proxy node, so that the external platform locates the operation task according to the second task identifier in the acquisition request, and obtains the log corresponding to the operation task, or status information;

   Receive the log or status information corresponding to the acquisition request that the external platform feeds back to the preset agent node, and adjust the status of the operation task according to the log or the status information until the execution of the operation task is completed.
5. The task processing method based on platform interaction according to claim 1, wherein the state information of the operation task fed back by the external platform is received, and the state of the operation task is flipped according to the state information until the The steps to complete the execution of the operation task include:

   Receive the second task identifier of the operation task fed back by the external platform, and generate an asynchronous response instance corresponding to the second task identifier, wherein a listener is set in the asynchronous response instance, and a callback method is set in the listener ；

   When the asynchronous response instance monitors the trigger event of the operation task corresponding to the second task identifier, the callback method is executed and the state of the operation task is adjusted according to the trigger event until the execution of the operation task is completed.
6. The task processing method based on platform interaction according to claim 1, wherein the state information of the operation task fed back by the external platform is received, and the state of the operation task is flipped according to the state information until the After the completion of the execution of the operation task, the steps include:

   When it is detected that the execution of the operation task is completed, the execution result information of the operation task is fed back to the user terminal, and the resources of the operation task are released.
7. The task processing method based on platform interaction according to any one of claims 1 to 6, wherein the task processing method based on platform interaction further comprises:

   When receiving the offline request of the external platform, obtain the platform ID corresponding to the offline request of the external platform;

   Query the plug-in directory of the microservice platform, obtain the jar package corresponding to the platform identifier, delete the jar package, and offline the external platform corresponding to the platform identifier.
8. A task processing system based on platform interaction, wherein the task processing system based on platform interaction includes a microservice platform and an external platform that are communicatively connected, and the interaction between the microservice platform and the external platform implements the following steps:

   When the microservice platform receives the operation task, the microservice platform obtains the task information corresponding to the operation task;

   The microservice platform judges whether to transfer the operation task according to the task information;

   If the operation task is to be transferred, the microservice platform submits the operation task to an external platform through the preset agent node, so that the external platform can process the operation task;

   The external platform executes the operation task to generate the log or status information corresponding to the operation task, and the external platform calls the network interface of the microservice platform to feed back the log or the status information;

   When the microservice platform detects that the network interface is called, the microservice platform obtains the log or the status information fed back by the network interface;

   The microservice platform performs state inversion of the operation task according to the log or the status information until the execution of the operation task is completed.
9. A task processing device based on platform interaction, wherein the task processing device based on platform interaction includes:

   The request receiving module is configured to obtain task information corresponding to the operation task when the operation task is received;

   The transfer judgment module is used for judging whether to transfer the operation task according to the task information;

   A task forwarding module, configured to, if the operation task is to be transferred, submit the operation task to an external platform through the preset agent node, so that the external platform can process the operation task;

   The receiving and turning module is configured to receive the state information of the operation task fed back by the external platform, and perform state inversion of the operation task according to the state information until the execution of the operation task is completed.
10. A task processing device based on platform interaction, wherein the task processing device based on platform interaction includes: a memory, a processor, and platform interaction-based task processing stored in the memory and running on the processor A program, when the task processing program based on platform interaction is executed by the processor, the steps of the task processing method based on platform interaction according to any one of claims 1 to 7 are realized.
11. A computer-readable storage medium, wherein a task processing program based on platform interaction is stored on the computer-readable storage medium, and the task processing program based on platform interaction is implemented by a processor as in claims 1 to 7 Steps of any of the task processing methods based on platform interaction.