CN116954736A

CN116954736A - Method and device for acquiring data between application programs, electronic equipment and medium

Info

Publication number: CN116954736A
Application number: CN202210388062.9A
Authority: CN
Inventors: 乔新程
Original assignee: Beijing Co Wheels Technology Co Ltd
Current assignee: Beijing Co Wheels Technology Co Ltd
Priority date: 2022-04-13
Filing date: 2022-04-13
Publication date: 2023-10-27

Abstract

The disclosure provides a method, a device, electronic equipment and a medium for acquiring data among application programs, wherein the method comprises the following steps: receiving a call request sent by a first application program; the calling request carries the position information of the second application program, the target running state of the second application program and the target file path; monitoring the second application program according to the position information of the second application program; under the condition that the running state of the second application program accords with the target running state is monitored, reading target data in the second application program according to the target file path; and returning the target data to the first application program. Therefore, the calling request of the first application program is received through the components independent of the first application program and the second application program, the target data of the second application program is obtained according to the calling request, and the target data is returned to the first application program, so that the complexity of component development codes can be reduced, and the difficulty of component debugging is reduced.

Description

Method and device for acquiring data between application programs, electronic equipment and medium

Technical Field

The present disclosure relates to the field of information processing technologies, and in particular, to a method and an apparatus for acquiring data between application programs, an electronic device, and a medium.

Background

Kubernetes, K8S for short, is an open source for managing containerized applications on multiple hosts in a cloud platform. Kubernetes makes deploying containerized applications simple and efficient, and provides a mechanism for application deployment, planning, updating, and maintenance.

OAM (Open Application Model ) defines some specifications and standards for cloud native applications from which developers can define application components in the open application model.

The KubeVela is an out-of-box and modern application delivery and management platform, so that the application delivery for the hybrid cloud/multi-cloud environment becomes very simple and efficient. Wherein, kubeVela is constructed based on Kubernetes and OAM technology.

Kubebuilder, an SDK (Software Development Kit ) that uses CRDs (Custom Resource Definition, definition of custom resources) to build K8S APIs (Application Programming Interface, application program interfaces), can provide scaffold tools to initialize CRDs engineering, automatically generate code and configuration, and provide clients K8S go-clients at the bottom of the code library package.

In delivering Kubernetes native resources using KubeVela, there may be scenarios where application information is acquired across applications, such as application 1 acquiring information related to available application 2.

For example, when a new application service of an on VM (Virtual Machine) needs to be released, two steps can be divided: 1. applying for VM resources; 2. and deploying and releasing the new application on the applied VM resources. However, since the application for VM resources has many scenarios, in order to enable multiplexing VM resources, the above step 1 may be independently extracted from an application for use, so that in step 2, to obtain the data (such as IP) in step 1, it is to obtain information across applications.

In the related art, the current processing manner of KubeVela is: the acquisition of relevant information of available applications 2 across applications is achieved using workflow plug-ins-on-apps built into application 1. However, in the above manner, the plug-in is highly bound with the application in the manner of embedding the plug-in the application, so that not only is the development code complex, but also the debugging is difficult.

Disclosure of Invention

The present disclosure provides a method, an apparatus, an electronic device, and a medium for acquiring data between application programs, so as to solve at least one of the technical problems in the related art to a certain extent. The technical scheme of the present disclosure is as follows:

According to an aspect of the present disclosure, there is provided a method for acquiring data between applications, including:

receiving a call request sent by a first application program; the call request carries the position information of the second application program, the target running state of the second application program and the target file path;

monitoring the second application program according to the position information of the second application program;

reading target data in the second application program according to the target file path under the condition that the running state of the second application program is monitored to be in accordance with the target running state;

and returning the target data to the first application program.

According to another aspect of the present disclosure, there is provided another inter-application data acquisition method, which is performed by a first application, including:

generating a calling request according to a second application program to which the data to be acquired belong;

sending the call request to a target component to call the target component to monitor the second application program, and reading target data in the second application program according to a target file path when the running state of the second application program is monitored to be in accordance with a target running state;

And acquiring the target data read by the target component.

According to still another aspect of the present disclosure, there is provided an inter-application data acquisition apparatus including:

the receiving module is used for receiving a call request sent by the first application program; the call request carries the position information of the second application program, the target running state of the second application program and the target file path;

the monitoring module is used for monitoring the second application program according to the position information of the second application program;

the reading module is used for reading target data in the second application program according to the target file path under the condition that the running state of the second application program is monitored to be in accordance with the target running state;

and the return module is used for returning the target data to the first application program.

According to still another aspect of the present disclosure, there is provided another inter-application data acquisition apparatus including:

the generating module is used for generating a calling request according to a second application program to which the data to be acquired belong;

the processing module is used for sending the calling request to the target component so as to call the target component to monitor the second application program, and reading target data in the second application program according to a target file path when the running state of the second application program is monitored to be in accordance with the target running state;

And the acquisition module is used for acquiring the target data read by the target component.

According to still another aspect of the present disclosure, there is provided an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the method for acquiring data between applications set forth in the above aspect of the present disclosure or performs the method for acquiring data between applications set forth in the above aspect of the present disclosure when the processor executes the program.

According to still another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium of computer instructions for causing the computer to execute the method for acquiring data between applications set forth in the above aspect of the present disclosure or to execute the method for acquiring data between applications set forth in the above aspect of the present disclosure.

According to still another aspect of the present disclosure, there is provided a computer program product including a computer program which, when executed by a processor, implements the method for acquiring data between applications set forth in the above aspect of the present disclosure, or implements the method for acquiring data between applications set forth in the above aspect of the present disclosure.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

receiving a call request sent by a first application program; the calling request carries the position information of the second application program, the target running state of the second application program and the target file path; monitoring the second application program according to the position information of the second application program; under the condition that the running state of the second application program accords with the target running state is monitored, reading target data in the second application program according to the target file path; and returning the target data to the first application program. Therefore, the calling request of the first application program is received through the components independent of the first application program and the second application program, the target data of the second application program is obtained according to the calling request, and the target data is returned to the first application program, so that the complexity of component development codes can be reduced, and the difficulty of component debugging is reduced. That is, in the present disclosure, the components are decoupled from the application program, and cross-application data acquisition is implemented through the independent components, so that the code complexity and maintenance difficulty of the components and the applications can be reduced, and the difficulty of component debugging is reduced.

Additional aspects and advantages of the disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the disclosure.

Drawings

The foregoing and/or additional aspects and advantages of the present disclosure will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a flowchart of a method for acquiring data between applications according to an embodiment of the disclosure;

fig. 2 is a flowchart of a method for acquiring data between applications according to a second embodiment of the disclosure;

fig. 3 is a flowchart of a method for acquiring data between applications according to a third embodiment of the present disclosure;

fig. 4 is a flowchart of a method for acquiring data between applications according to a fourth embodiment of the present disclosure;

fig. 5 is a flowchart of a method for acquiring data between applications according to a fifth embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an inter-application data acquisition device according to a sixth embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of an inter-application data acquisition device according to a seventh embodiment of the present disclosure;

fig. 8 illustrates a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the invention.

Detailed Description

Embodiments of the present disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present disclosure and are not to be construed as limiting the present disclosure.

In the related art, in the process of delivering Kubernetes native resources using KubeVela, there may be a scenario of acquiring application information across applications.

For example, when a new application service of an on VM (Virtual Machine) needs to be released, two steps can be divided:

1. applying for VM resources;

2. and deploying and releasing the new application on the applied VM resource.

However, since the application for VM resources has many scenarios, in order to enable multiplexing VM resources, the above step 1 may be independently extracted from an application for use, so that in step 2, to obtain the data (such as IP) in step 1, it is to obtain information across applications.

In the related art, the current processing mode of KubeVela is as follows: the workflow plug-in-on-app built in the application is used to realize that related information of other applications is acquired across applications. However, the above approach may cause the following problems:

(1) Workflow blockage can be caused, so that the user must wait for the last application resource to be successfully created before proceeding downwards, and the operation efficiency is reduced;

(2) The plug-in is highly bound with the application in a mode of embedding the plug-in the application, so that development and coding are complex, and debugging is difficult.

In view of the above problems, the present disclosure proposes a method, an apparatus, an electronic device, and a medium for acquiring data between applications. Before describing embodiments of the present disclosure in detail, for ease of understanding, general technical words are first introduced:

the Pod resource type is the minimum unit of run container and schedule. Wherein the same Pod may run multiple containers simultaneously, which may share some resources.

The Deployment resource type is the most common stateless application controller and supports operations such as expanding and contracting capacity, rolling updating and the like of the application.

The Servcie resource type provides a fixed access interface for the Pod object which is flexible and has life cycle, and is used for service discovery and service access.

The following describes a method, an apparatus, an electronic device, and a medium for acquiring data between applications according to an embodiment of the present disclosure with reference to the accompanying drawings.

Fig. 1 is a flowchart of a method for acquiring data between applications according to an embodiment of the disclosure.

The data acquisition method among the application programs can be applied to a target component which is independent of the first application program and the second application program.

As shown in fig. 1, the inter-application data acquisition method may include the steps of:

step 101, receiving a call request sent by a first application program; the call request carries the position information of the second application program, the target running state of the second application program and the target file path.

In the embodiment of the disclosure, the second application is different from the first application, for example, the second application may be any application (may also be referred to as a resource, or an application resource) in the K8S cluster that is different from the first application.

In the embodiment of the present disclosure, the location information of the second application program may be, for example, a coordinate location of the second application program.

In an embodiment of the present disclosure, the target running state of the second application is used to indicate that the second application is available when the running state of the second application meets the target running state.

In the embodiment of the present disclosure, the target file path is used to indicate a location or a storage location of data (referred to as target data in the present disclosure) that is focused on or required by the first application program, that is, the target file path is used to indicate a storage location of the target data in the second application program.

In the embodiment of the present disclosure, when a first application needs to acquire related data (referred to as target data in the present disclosure) of another application, for example, a second application, the first application may send a call request to a target component, and correspondingly, the target component may receive the call request sent by the first application, where the call request may carry location information of the second application, a target running state of the second application, and a target file path.

It should be explained that the first application may include a plurality of components in parallel, where the plurality of components may include, but is not limited to, two, and in one possible implementation manner of the embodiment of the present disclosure, the first application may send, through at least one component in the plurality of components in parallel, a call request to a target component, and correspondingly, the target component may receive the call request sent by at least one component in the plurality of components of the first application.

It can be understood that the multiple components are parallel, so that the running efficiency of the first application program can be improved, and when at least one of the multiple components in parallel sends a call request to the target component, other components, which have no dependency relationship with the at least one component, in the multiple components in parallel can process other data, so that the multiple components can be executed concurrently, the blocking waiting condition can not be caused, and the running efficiency of the first application program is improved.

And 102, monitoring the second application program according to the position information of the second application program.

In the embodiment of the disclosure, after receiving the call request sent by the first application program, the target component may respond to the call request and monitor the second application program according to the location information of the second application program. For example, the target component may monitor a CR (Custom Resource) change of the second application, etc., monitor a running state of the second application, etc., according to location information of the second application, which is not limited by the present disclosure.

And step 103, reading target data in the second application program according to the target file path under the condition that the running state of the second application program accords with the target running state.

In the embodiment of the disclosure, when the target component monitors that the running state of the second application program accords with the target running state, it indicates that the second application program is available, and the target component may read target data in the second application program according to the target file path.

In a possible implementation manner of the embodiment of the present disclosure, when the target component monitors that the running state of the second application program does not conform to the target running state, at this time, it indicates that the second application program is not available, the target component may continue to monitor the running state of the second application program until it monitors that the running state of the second application program conforms to the target running state, and the target component may read the target data in the second application program according to the target file path.

And 104, returning the target data to the first application program.

In the embodiment of the disclosure, after the target component reads the target data in the second application program, the target data may be returned to the first application program.

According to the method for acquiring the data between the application programs, the calling request sent by the first application program is received; the calling request carries the position information of the second application program, the target running state of the second application program and the target file path; monitoring the second application program according to the position information of the second application program; under the condition that the running state of the second application program accords with the target running state is monitored, reading target data in the second application program according to the target file path; and returning the target data to the first application program. Therefore, the calling request of the first application program is received through the components independent of the first application program and the second application program, the target data of the second application program is obtained according to the calling request, and the target data is returned to the first application program, so that the complexity of component development codes can be reduced, and the difficulty of component debugging is reduced. That is, in the present disclosure, the components are decoupled from the application program, and cross-application data acquisition is implemented through the independent components, so that the code complexity and maintenance difficulty of the components and the applications can be reduced, and the difficulty of component debugging is reduced.

In order to clearly illustrate how the target component in any embodiment of the present disclosure monitors the second application according to the location information of the second application, the present disclosure further provides a method for acquiring data between applications.

Fig. 2 is a flowchart of a method for acquiring data between applications according to a second embodiment of the disclosure.

As shown in fig. 2, the inter-application data acquisition method may include the steps of:

step 201, receiving a call request sent by a first application program; the call request carries the position information of the second application program, the target running state of the second application program and the target file path.

The implementation of step 201 may refer to the implementation of any embodiment of the present disclosure, which is not described herein.

And 202, analyzing the position information to obtain resource path version information, resource type and resource name information.

In the embodiment of the present disclosure, the resource path Version information is used to indicate a Version to which the resource path belongs, for example, the resource path Version information may be API (Application Programming Interface ) Version (Version) information.

In the embodiment of the present disclosure, the resource type is used to indicate the type to which the resource belongs, for example, pod, deployment, service in the K8S resource type may be included, which is not limited by the present disclosure.

In the embodiment of the present disclosure, the resource name information may include a resource name (resource name) and a NameSpace (NameSpace) to which the resource name belongs.

In the embodiment of the disclosure, the location information of the second application program may be parsed to obtain resource path version information, resource type and resource name information.

As an example, taking a target component as a K8S resource transport component for example, and referring to the target component or the K8S resource transport component as a K8S-porter, the call request may include:

and step 203, accessing the corresponding resource path according to the resource path version information to obtain a second application program matched with the resource type and the resource name information under the resource path.

In the embodiment of the disclosure, the target component may access the corresponding resource path according to the resource path version information to determine the second application program matching with the resource type and the resource name information under the resource path, so that the target component may monitor the second application program.

Step 204, monitor the running state of the second application.

In the embodiment of the disclosure, after determining the second application program, the target component may monitor the running state of the second application program.

It should be noted that, in the actual running process, the running state of the second application may change, in one possible implementation manner of the embodiment of the present disclosure, in order to effectively and accurately obtain the running state of the second application, the target component may periodically monitor the running state of the second application, determine whether the running state of the second application changes, and in the case that the running state of the second application changes, the target component may read the running state of the second application after the change.

The listening period may be preset, and may be, for example, 10s, 15s, or the like, which is not limited in this disclosure.

In step 205, under the condition that the running state of the second application program accords with the target running state, the target data in the second application program is read according to the target file path.

And step 206, returning the target data to the first application program.

The execution of steps 205 to 206 may refer to the execution of any embodiment of the present disclosure, and will not be described herein.

According to the data acquisition method among the application programs, the resource path version information, the resource type and the resource name information are obtained through analysis of the position information; accessing a corresponding resource path according to the resource path version information to obtain a second application program matched with the resource type and the resource name information under the resource path; and monitoring the running state of the second application program. Therefore, the position information is analyzed, the resource path version information, the resource type and the resource name information are obtained, the target component can effectively determine the second application program based on the source path version information, the resource type and the resource name information, and the target component can effectively monitor the running state of the second application program.

In order to clearly illustrate how the target component monitors the running state of the second application in any embodiment of the present disclosure, the present disclosure further proposes a method for acquiring data between applications.

Fig. 3 is a flowchart of a method for acquiring data between applications according to a third embodiment of the present disclosure.

As shown in fig. 3, the inter-application data acquisition method may include the steps of:

step 301, receiving a call request sent by a first application program; the call request carries the position information of the second application program, the target running state of the second application program and the target file path.

Step 302, parsing the location information to obtain resource path version information, resource type and resource name information.

And step 303, accessing the corresponding resource path according to the resource path version information to obtain a second application program matched with the resource type and the resource name information under the resource path.

The execution of steps 301 to 303 may refer to the execution of any embodiment of the present disclosure, and will not be described herein.

Step 304, periodically monitor whether the running state of the second application program changes.

In the embodiment of the present disclosure, the listening period of the target component may be preset, for example, the period may be 10s, 15s, and the like, which is not limited in the present disclosure.

It should be noted that, in the actual running process, the running state of the second application may change, so that, in order to effectively and accurately obtain the running state of the second application, the target component may periodically monitor the running state of the second application to determine whether the running state of the second application changes.

In step 305, when there is a change in the running state of the second application, the running state of the second application after the change is read.

In the embodiment of the present disclosure, the target component may read the running state of the second application after the change in the running state of the second application is monitored.

It should be explained that, when the target component periodically monitors the running state of the second application program, there may be a case that the running state of the second application program is not changed, so in another possible implementation manner of the embodiment of the present disclosure, when the running state of the second application program is not changed, it may be determined whether the running state of the second application program meets the target running state, if the running state of the second application program meets the target running state, the target component may execute the step 306 and the subsequent steps, and if the running state of the second application program does not meet the target running state, the target component may continue to execute the step of periodically monitoring whether the running state of the second application program is changed until the running state after the second application program is changed is the target running state, and may execute the step 306 and the subsequent steps.

And step 306, reading target data in the second application program according to the target file path under the condition that the running state of the second application program accords with the target running state.

In the embodiment of the disclosure, when the target component monitors that the running state of the second application program accords with the target running state, the target data in the second application program pointed to by the target file path can be determined according to the target file path, so that the target data can be read.

It should be explained that, in the case that the running state of the second application program changes, after the target component reads the running state of the second application program after the running state of the second application program changes, if it is determined that the running state of the second application program does not conform to the target running state, in another possible implementation manner of the embodiment of the disclosure, the target component may continue to execute the step of periodically monitoring whether the running state of the second application program changes until the running state of the second application program after the running state of the second application program changes conforms to the target running state, and then the target component may execute the step 306 and the subsequent steps.

Step 307, returning the target data to the first application.

The execution of steps 306 to 307 may refer to the execution of any embodiment of the disclosure, and will not be described herein.

According to the data acquisition method among the application programs, whether the running state of the second application program changes or not is monitored periodically; and under the condition that the running state of the second application program is changed, reading the running state of the second application program after the change. Therefore, the running state of the second application program can be timely, effectively and accurately acquired by periodically monitoring the running state of the second application program.

Corresponding to the above embodiment, the present disclosure also proposes a method for acquiring data between applications executed by a first application.

Fig. 4 is a flowchart of a method for acquiring data between applications according to a fourth embodiment of the present disclosure.

As shown in fig. 4, the inter-application data acquisition method may be executed by a first application, and may include the following steps:

step 401, generating a call request according to a second application program to which the data to be acquired belongs.

In the embodiment of the present disclosure, the data to be acquired is data required by the first application program, and the data to be acquired is data in the second application program.

In the embodiment of the disclosure, the first application program may generate the call request according to the second application program to which the data to be acquired belongs.

In one possible implementation of the embodiment of the disclosure, the first application program may generate the call request according to the location information of the second application program, the target running state of the second application program, and the target file path storing the target data. The specific implementation process may be referred to the related description in the foregoing embodiments, which is not repeated herein.

And step 402, sending a call request to the target component to call the target component to monitor the second application program, and reading target data in the second application program according to the target file path under the condition that the running state of the second application program accords with the target running state.

In the embodiment of the disclosure, the target component may be a component that listens to the second application.

In the embodiment of the disclosure, the first application program may send a call request to the target component, and correspondingly, after receiving the call request, the target component may respond to the call request to monitor the second application program, and when the target component monitors that the running state of the second application program meets the target running state, the target component may read, according to the target file path, target data in the second application program pointed to by the target file path.

In step 403, the target data read by the target component is obtained.

In the embodiment of the disclosure, after the target component reads the target data, the target data may be returned to the first application program, so that the first application program obtains the target data read by the target component.

According to the method for acquiring the data among the application programs, a call request is generated through a first application program according to a second application program to which data to be acquired belong; sending a call request to a target component to call the target component to monitor a second application program, and reading target data in the second application program according to a target file path under the condition that the running state of the second application program accords with the target running state is monitored; and acquiring target data read by the target component. Therefore, the calling request of the first application program is received through the components independent of the first application program and the second application program, the target data of the second application program is obtained according to the calling request, and the target data is returned to the first application program, so that the complexity of component development codes can be reduced, and the difficulty of component debugging is reduced. That is, in the present disclosure, the components are decoupled from the application program, and cross-application data acquisition is implemented through the independent components, so that the code complexity and maintenance difficulty of the components and the applications can be reduced, and the difficulty of component debugging is reduced.

In order to clearly explain how the first application program sends the call request to the target component in the above embodiments of the present disclosure, the present disclosure further provides a method for acquiring data between application programs executed by the first application program.

Fig. 5 is a flowchart of a method for acquiring data between applications according to a fifth embodiment of the present disclosure.

As shown in fig. 5, the inter-application data acquisition method may be executed by a first application, and may include the following steps:

step 501, a call request is generated according to a second application program to which the data to be acquired belongs.

The implementation of step 501 may refer to the implementation of any embodiment of the present disclosure, which is not described herein.

Step 502, in the case that the first application program includes multiple parallel components, sending, by the first component in the multiple parallel components, a call request to the target component, so as to call the target component to monitor the second application program.

In the disclosed embodiments, the first application may include multiple components in parallel. Wherein the number of components may include, but is not limited to, two, which is not limited by the present disclosure.

In the embodiment of the disclosure, the first component may be a component that sends a call request to the target component among multiple components in parallel. Wherein the number of the first components is at least one.

In the embodiment of the disclosure, in the case that the first application program includes multiple parallel components, a call request may be sent to the target component by the first component in the multiple parallel components to call the target component to realize interception of the second application program.

In step 503, in the process of waiting for the target component to return the target data corresponding to the call request, executing the second component which has no dependency relationship with the first component in the multiple components.

In the embodiment of the disclosure, in the process of waiting for the target component to return the target data corresponding to the call request, the second component may be executed, where the second component is a component that has no dependency relationship with the first component in the multiple parallel components.

It can be understood that the multiple components are parallel, so that the running efficiency of the first application program can be improved, and when at least one first component in the parallel multiple components sends a call request to the target component, a second component which has no dependency relationship with the at least one first component in the parallel multiple components can process other data, so that the multiple components can be executed concurrently, the blocking waiting condition is not caused, and the running efficiency of the first application program is improved.

In step 504, under the condition that the running state of the second application program accords with the target running state, the target data in the second application program is read according to the target file path.

In step 505, the target data read by the target component is obtained.

The execution of steps 504 to 505 may refer to the execution of any embodiment of the present disclosure, and will not be described herein.

It should be noted that, the disclosure is only illustrated with step 503 being performed before step 504, but the disclosure is not limited thereto, i.e. the disclosure does not limit the execution timing of step 503, for example, step 503 may be performed after step 504, or step 503 may be performed in parallel with step 504.

According to the inter-application data acquisition method, a call request is sent to a target component through a first component in a plurality of parallel components; and executing a second component which has no dependency relationship with the first component in the multiple components in the process of waiting for the target component to return the target data corresponding to the call request. Therefore, a plurality of components in the first application program can be executed in parallel, the situation of blocking waiting is avoided, and therefore the running efficiency of the first application program is improved.

In any embodiment of the present disclosure, a target component is taken as a component for K8S resource transport, and the target component or the component for K8S resource transport is referred to as a K8S-porter, and the target component can transport any resource data to any application in a K8S cluster, so that a specific process is described in the following steps:

1) First define a CRD (Custom Resource Definition, definition of custom resources):

wherein Target describes location information of the second application, based on which the Target component can monitor the second application; condition describes a target running state of the second application, the target running state being used to indicate that the running state of the second application is available when the running state meets the target running state; fieldPath describes a target file path based on which a target component may determine target data in a second application.

2) The main logic of the target component or the k8s-porter component is used for developing a tuning method, the target component or the k8s-porter component can monitor CR (Custom Resource) change, and when the running state of the second application program accords with the target running state described by the Condition, target data at the position of the FieldPath can be obtained; when the running state of the second application program does not conform to the target running state described by the Condition, the target component or the k8s-porter component can be put into the tuning queue again, and the next period (the period can be customized, such as 10s, etc.) is waited for, and the above monitoring process is repeatedly executed until the running state of the second application program conforms to the target running state described by the Condition.

Wherein, step 1) and step 2) can be developed using Kubebuilder.

3) And publishing the developed CRD and the Controller to the K8S cluster, so that whether the running state of the K8S-porter resource changes can be monitored by using the target component or the K8S-porter component.

4) Based on the KubeVela, a target component or a K8s porter component is developed, and the main logic of the target component or the K8s porter component is to monitor whether the running state of the K8s-porter resource (i.e. the second application program) changes, and when the running state is the target running state, it is indicated that the K8s-porter resource (i.e. the second application program) is available or healthy, at this time, target data in the K8s-porter resource (i.e. the second application program) can be acquired, and the target data can be transferred to other application services for use, such as transferring the target data to the first application program for use.

5) The target component or the K8sPorter component is published into the K8S cluster.

After the above is finished, the target component or the K8sPorter component can be normally used, and the K8S-porter component can be normally called to acquire data of any resource in the K8S cluster, and a workflow function of the KubeVela is not required to be used.

In summary, by developing a component for K8S resource transportation (namely, a K8sPorter component or a target component), components with strong dependency relationship in an application program can be executed concurrently, the situation of blocking waiting is avoided, the running efficiency of the application program is effectively improved, in actual use, data of any resource in a K8S cluster is obtained through the K8S-porter component, and the data of other resources in the K8S cluster are obtained without a plug-in the application program, so that the development and debugging difficulty is reduced, and the development efficiency is improved.

Corresponding to the method for acquiring data between applications provided in the embodiments of fig. 1 to 3, the present disclosure further provides an apparatus for acquiring data between applications, and since the apparatus for acquiring data between applications provided in the embodiments of the present disclosure corresponds to the method for acquiring data between applications provided in the embodiments of fig. 1 to 3, the implementation of the method for acquiring data between applications is also applicable to the apparatus for acquiring data between applications provided in the embodiments of the present disclosure, which is not described in detail in the embodiments of the present disclosure.

Fig. 6 is a schematic structural diagram of an inter-application data acquisition device according to a sixth embodiment of the disclosure.

As shown in fig. 6, the inter-application data acquisition apparatus 600 may include: a receiving module 601, a listening module 602, a reading module 603 and a returning module 604.

The receiving module 601 is configured to receive a call request sent by a first application program; the call request carries the position information of the second application program, the target running state of the second application program and the target file path.

And the monitoring module 602 is configured to monitor the second application according to the location information of the second application.

And the reading module 603 is configured to read the target data in the second application program according to the target file path if it is monitored that the running state of the second application program accords with the target running state.

A return module 604 for returning the target data to the first application.

In one possible implementation of the embodiment of the disclosure, a listening module 602 is configured to: analyzing the position information to obtain resource path version information, resource type and resource name information; accessing a corresponding resource path according to the resource path version information to obtain a second application program matched with the resource type and the resource name information under the resource path; and monitoring the running state of the second application program.

In one possible implementation of the embodiment of the disclosure, a listening module 602 is configured to: periodically monitoring whether the running state of the second application program changes; and under the condition that the running state of the second application program is changed, reading the running state of the second application program after the change.

In one possible implementation of an embodiment of the disclosure, the apparatus 600 may further include:

and the execution module is used for continuously executing the step of periodically monitoring whether the running state of the second application program changes or not until the running state of the second application program changes meets the target running state under the condition that the running state of the second application program does not change or the running state of the second application program after the second application program changes does not meet the target running state.

In one possible implementation manner of the embodiment of the present disclosure, the first application program includes a plurality of components in parallel, and the receiving module 601 is configured to: a call request sent by at least one of a plurality of components of a first application is received.

The inter-application data acquisition device of the embodiment of the disclosure receives a call request sent by a first application; the calling request carries the position information of the second application program, the target running state of the second application program and the target file path; monitoring the second application program according to the position information of the second application program; under the condition that the running state of the second application program accords with the target running state is monitored, reading target data in the second application program according to the target file path; and returning the target data to the first application program. Therefore, the calling request of the first application program is received through the components independent of the first application program and the second application program, the target data of the second application program is obtained according to the calling request, and the target data is returned to the first application program, so that the complexity of component development codes can be reduced, and the difficulty of component debugging is reduced. That is, in the present disclosure, the components are decoupled from the application program, and cross-application data acquisition is implemented through the independent components, so that the code complexity and maintenance difficulty of the components and the applications can be reduced, and the difficulty of component debugging is reduced.

Corresponding to the method for acquiring data between applications provided in the embodiments of fig. 4 to 5, the present disclosure further provides an apparatus for acquiring data between applications, and since the apparatus for acquiring data between applications provided in the embodiments of the present disclosure corresponds to the method for acquiring data between applications provided in the embodiments of fig. 4 to 5, the implementation of the method for acquiring data between applications is also applicable to the apparatus for acquiring data between applications provided in the embodiments of the present disclosure, which is not described in detail in the embodiments of the present disclosure.

Fig. 7 is a schematic structural diagram of an inter-application data acquisition device according to a seventh embodiment of the disclosure.

As shown in fig. 7, the inter-application data acquisition apparatus 700 may include: a generating module 701, a processing module 702 and an acquiring module 703.

The generating module 701 is configured to generate a call request according to a second application program to which the data to be acquired belongs.

The processing module 702 is configured to send a call request to the target component, so as to call the target component to monitor the second application program, and read target data in the second application program according to the target file path when it is monitored that the running state of the second application program meets the target running state.

The acquiring module 703 is configured to acquire the target data read by the target component.

In one possible implementation of the embodiment of the disclosure, the generating module 701 is configured to: and generating a call request according to the position information of the second application program, the target running state of the second application program and the target file path for storing the target data.

In one possible implementation of the embodiments of the present disclosure, the processing module 702 is configured to: sending a call request to a target component through a first component in the plurality of components in parallel; and executing a second component which has no dependency relationship with the first component in the multiple components in the process of waiting for the target component to return the target data corresponding to the call request.

According to the data acquisition device among the application programs, a call request is generated according to a second application program to which data to be acquired belong; sending a call request to a target component to call the target component to monitor a second application program, and reading target data in the second application program according to a target file path under the condition that the running state of the second application program accords with the target running state is monitored; and acquiring target data read by the target component. Therefore, the calling request of the first application program is received through the components independent of the first application program and the second application program, the target data of the second application program is obtained according to the calling request, and the target data is returned to the first application program, so that the complexity of component development codes can be reduced, and the difficulty of component debugging is reduced. That is, in the present disclosure, the components are decoupled from the application program, and cross-application data acquisition is implemented through the independent components, so that the code complexity and maintenance difficulty of the components and the applications can be reduced, and the difficulty of component debugging is reduced.

In order to implement the foregoing embodiments, the disclosure further provides an electronic device, which is characterized by including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements the data acquisition method between application programs according to any of the foregoing embodiments of the disclosure when executing the program.

In order to implement the above-described embodiments, the present disclosure also proposes a non-transitory computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method for acquiring data between applications as proposed in any of the foregoing embodiments of the present disclosure.

To achieve the above embodiments, the present disclosure further provides a computer program product which, when executed by a processor, performs a method for acquiring data between applications as set forth in any of the foregoing embodiments of the present disclosure.

As shown in fig. 8, the electronic device 12 is in the form of a general purpose computing device. Components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.

Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include industry Standard architecture (Industry Standard Architecture; hereinafter ISA) bus, micro channel architecture (Micro Channel Architecture; hereinafter MAC) bus, enhanced ISA bus, video electronics standards Association (Video Electronics Standards Association; hereinafter VESA) local bus, and peripheral component interconnect (Peripheral Component Interconnection; hereinafter PCI) bus.

Electronic device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

Memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter: RAM) 30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard disk drive"). Although not shown in fig. 6, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a compact disk read only memory (Compact Disc Read Only Memory; hereinafter CD-ROM), digital versatile read only optical disk (Digital Video Disc Read Only Memory; hereinafter DVD-ROM), or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the various embodiments of the disclosure.

A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods in the embodiments described in this disclosure.

The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the electronic device 12, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks, such as a local area network (Local Area Network; hereinafter: LAN), a wide area network (Wide Area Network; hereinafter: WAN) and/or a public network, such as the Internet, via the network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 over the bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing the methods mentioned in the foregoing embodiments.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present disclosure. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present disclosure, the meaning of "a plurality" is at least two, such as two, three, etc., unless explicitly specified otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and additional implementations are included within the scope of the preferred embodiment of the present disclosure in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present disclosure.

Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. As with the other embodiments, if implemented in hardware, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.

Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.

Furthermore, each functional unit in the embodiments of the present disclosure may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like. Although embodiments of the present disclosure have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the present disclosure, and that variations, modifications, alternatives, and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the present disclosure.

Claims

1. A method for acquiring data between applications, comprising the steps of:

and returning the target data to the first application program.

2. The method of claim 1, wherein listening for the second application based on the location information of the second application comprises:

Analyzing the position information to obtain resource path version information, resource type and resource name information;

accessing a corresponding resource path according to the resource path version information to obtain the second application program matched with the resource type and the resource name information under the resource path;

and monitoring the running state of the second application program.

3. The method of claim 2, wherein the listening for the running state of the second application comprises:

periodically monitoring whether the running state of the second application program changes;

and under the condition that the running state of the second application program is changed, reading the running state of the second application program after the change.

4. A method according to claim 3, characterized in that the method further comprises:

and continuously executing the step of periodically monitoring whether the running state of the second application program changes or not until the running state of the second application program after changing accords with the target running state under the condition that the running state of the second application program does not change or the running state of the second application program after changing does not accord with the target running state.

5. A method for inter-application data acquisition, the method being performed by a first application and comprising the steps of:

and acquiring the target data read by the target component.

6. The method of claim 5, wherein the sending the call request to the target component comprises:

sending the call request to the target component through a first component in the plurality of components in parallel;

and executing a second component which has no dependency relationship with the first component in the multiple components in the process of waiting for the target component to return the target data corresponding to the call request.

7. An inter-application data acquisition apparatus, the apparatus comprising:

8. An inter-application data acquisition apparatus for use with a first application, the apparatus comprising:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of data acquisition between applications according to any one of claims 1-4 or the method of data acquisition between applications according to claim 5 or 6 when executing the program.

10. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that the program, when executed by a processor, implements the inter-application data acquisition method according to any one of claims 1 to 4, or implements the inter-application data acquisition method according to claim 5 or 6.

11. A computer program product, characterized in that the instructions in the computer program product, when executed by a processor, perform the inter-application data acquisition method according to any one of claims 1-4, or the inter-application data acquisition method according to claim 5 or 6.