CN117331600A - Data interaction self-adaption method for heterogeneous software system - Google Patents

Data interaction self-adaption method for heterogeneous software system Download PDF

Info

Publication number
CN117331600A
CN117331600A CN202311470468.2A CN202311470468A CN117331600A CN 117331600 A CN117331600 A CN 117331600A CN 202311470468 A CN202311470468 A CN 202311470468A CN 117331600 A CN117331600 A CN 117331600A
Authority
CN
China
Prior art keywords
interface
configuration
judges
message
namely
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311470468.2A
Other languages
Chinese (zh)
Inventor
李文续
薛鹏
李洪营
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur General Software Co Ltd
Original Assignee
Inspur General Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Inspur General Software Co Ltd filed Critical Inspur General Software Co Ltd
Priority to CN202311470468.2A priority Critical patent/CN117331600A/en
Publication of CN117331600A publication Critical patent/CN117331600A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/76Adapting program code to run in a different environment; Porting

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The invention relates to the technical field of software, in particular to a data interaction self-adaption method of a heterogeneous system of software, computer equipment and a storage medium. The method comprises the following steps: s10, defining a form and related field information; s20, identifying interface information, carrying out interface configuration, and analyzing the interface configuration; s30, verifying the interface, checking whether the interface configuration meets the requirements, and recording an operation log. The invention can enable the application personnel to quickly, efficiently and accurately interact data with the heterogeneous software system.

Description

Data interaction self-adaption method for heterogeneous software system
Technical Field
The present invention relates to the field of software technologies, and in particular, to a data interaction adaptive method, a computer device, and a storage medium for a heterogeneous software system.
Background
Heterogeneous systems refer to a collection of systems spanning different operating system platforms, different database platforms, and different application server platforms, and may also be understood as a development environment for a multi-technology environment. It features that two or more independent systems with different techniques can complete the processing of one service together, for example, the data from different clients can be processed by different operation systems, and after different application processing, the final result is stored in different databases.
The different technologies can realize the work of cross-system and cross-platform, can effectively solve the problem of sharing and integrating the enterprise information and the data on various technical platforms, and can better improve the enterprise information management efficiency.
The most important of heterogeneous systems is the software development environment. The software development needs to meet different technical conditions, and if a heterogeneous system is adopted, the optimal performance can be obtained on different platforms only by meeting the minimum technical requirements. Thus, a comprehensive unified test can be implemented on different platforms.
In the development work of the system, the requirement of data interaction with a heterogeneous software system often occurs, the data interaction is embodied in an interface form, and if the system is developed by a back-end code method, time and labor consumption can occur, for example, the interface is changed, the back-end code is required to be changed in a large probability, and the service is restarted. In addition, the number of interfaces is large, unified management is inconvenient, and if one of the interfaces is changed, all functions cannot be used in the restarting service process, so that time, energy and resources are wasted.
Disclosure of Invention
In order to solve the technical problems in the prior art, the invention provides a data interaction self-adaption method of a software heterogeneous system, computer equipment and a storage medium.
In order to achieve the above object, the embodiment of the present invention provides the following technical solutions:
in a first aspect, in one embodiment provided by the present invention, a software heterogeneous system data interaction adaptive method is provided, and the method includes the following steps:
s10, defining a form and related field information;
s20, identifying interface information, carrying out interface configuration, and analyzing the interface configuration;
s30, verifying the interface, checking whether the interface configuration meets the requirements, and recording an operation log.
As a further aspect of the present invention, the identifying interface information, performing interface configuration, and analyzing interface configuration includes:
identifying interface information, carrying out interface definition A101, and recording interface basic information, wherein the basic information comprises an interface address, a request type, a parameter type and the like;
interface setting A102 is performed to configure the request message field.
As a further aspect of the present invention, the configuring the request packet field includes performing a fetch configuration for each request packet field.
As a further aspect of the present invention, the step S30 of verifying the interface, checking whether the configuration of the interface meets the requirement, and recording the operation log includes:
s301, judging whether a field is nested with A103;
if A103 judges yes, carrying out parameter configuration A104;
if the A103 judges no, judging whether the current interface has a front interface or simply writes back the A109;
if A109 judges yes, interface bus configuration A110 is carried out; the interface bus configuration A110 comprises a configuration before the current interface is executed and a configuration after the current interface is successfully executed; and judging whether the return message A111 needs to be analyzed, namely whether the interface return message needs to be converted into the form field information, and storing and displaying.
If the A109 judges no, judging whether the return message A111 needs to be analyzed or not;
if A111 judges yes, then the analysis interface is set to A112, namely the returned message field is matched with the database field one by one, and the two types are divided into an object and an array.
If A111 judges no, then carry out interface content verification A123, namely according to the configuration information, get the request message.
It is determined whether or not the requirement a124 is met.
If A124 determines no, it is necessary to complete the information starting from interface definition A101.
If A124 determines yes, an interface call A125 is made.
S302, recording an interface call log A126.
As a further aspect of the present invention, the parameters form a configuration a104, including:
judging whether the parameter type is an object A105;
if A105 judges yes, a value A106 is taken, namely a piece of data meeting the condition is taken from the fetch table, and request message field assignment is carried out;
if the A106 judges that the request message is not processed, the A107 is circularly fetched, namely all data meeting the condition are fetched from the fetch table, and the request message field is circularly fetched;
judging whether the request parameters in the parameter composition are nested with A108, namely whether the request parameter field consists of an object and an array and is not further processed;
if A108 judges yes, then parameter constitution configuration A104 is carried out, namely recursion reference is carried out;
if A108 determines no, it is referenced by the fields in interface setting A102 and then continues to determine if there are more nested fields A103 that have not yet been processed.
As a further aspect of the present invention, after the parsing interface setting a112, the method further includes:
judging whether the parameter type is an object A113;
if the A113 judges that the message is the return message, taking and storing a piece of data;
if the A113 judges that the message is not the data, circularly taking the returned message data for storage;
judging whether the return message is nested with A116, namely whether the return message field consists of an object and an array and is not further processed;
if A116 judges yes, then analyzing parameter to form A118, namely analyzing the field as the independent return message content, and dividing the field into two types of object and array;
if the A116 judges no, the analysis interface verification A117 is carried out, namely, the verification is carried out by using a return message according to analysis configuration information;
it is determined whether or not the requirement a124 is met.
As a further aspect of the present invention, after the analysis parameter forms a118, the method further includes:
judging whether the analysis parameter type is an object A119;
if A119 judges yes, a piece of data in the returned message parameters is taken and stored A120;
if the judgment of A119 is negative, all data in the returned message parameters are taken and stored A121.
As a further scheme of the present invention, if the judgment of A119 is negative, all data in the parameters of the returned message are fetched and stored A121, and then the method further comprises:
judging whether the return message parameter is nested with A122, namely whether the return message parameter field consists of an object and an array and is not further processed;
if A122 is judged to be yes, then resolving parameter construction A118 is carried out, namely recursive reference is carried out;
if A122 is negative, it is referenced by parse interface setting A112.
In a second aspect, in yet another embodiment provided by the present invention, a computer device is provided, including a memory storing a computer program and a processor implementing the steps of a software heterogeneous system data interaction adaptation method when the computer program is loaded and executed.
In a third aspect, in a further embodiment of the present invention, a storage medium is provided, storing a computer program, which when loaded and executed by a processor implements the steps of the software heterogeneous system data interaction adaptation method.
The technical scheme provided by the invention has the following beneficial effects:
the invention provides a software heterogeneous system data interaction self-adaption method, computer equipment and a storage medium, wherein the method comprises the following steps: s10, defining a form and related field information; s20, identifying interface information, carrying out interface configuration, and analyzing the interface configuration; s30, verifying the interface, checking whether the interface configuration meets the requirements, and recording an operation log. The invention can enable the application personnel to quickly, efficiently and accurately interact data with the heterogeneous software system.
These and other aspects of the invention will be more readily apparent from the following description of the embodiments. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are necessary for the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention and that other embodiments may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a software heterogeneous system data interaction adaptation method according to an embodiment of the invention.
FIG. 2 is a specific flow diagram of an example of software heterogeneous system data interaction adaptation in accordance with one embodiment of the present invention.
Fig. 3 is a flowchart of step S20 in the software heterogeneous system data interaction adaptive system according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The flow diagrams depicted in the figures are merely illustrative and not necessarily all of the elements and operations/steps are included or performed in the order described. For example, some operations/steps may be further divided, combined, or partially combined, so that the order of actual execution may be changed according to actual situations.
It is to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
In particular, embodiments of the present invention are further described below with reference to the accompanying drawings.
Referring to fig. 1 and fig. 2, fig. 1 is a flowchart of a software heterogeneous system data interaction adaptive method according to an embodiment of the present invention, and as shown in fig. 1, the software heterogeneous system data interaction adaptive method includes steps S10 to S30.
S10, defining a form and related field information, wherein the form and the related field information are used for recording and displaying information such as interface configuration, analysis interface configuration, operation log and the like;
s20, identifying interface information, carrying out interface configuration, and analyzing the interface configuration;
referring to fig. 3, in the embodiment of the present invention, S20 identifies interface information, performs interface configuration, analyzes interface configuration, and includes:
s201, identifying interface information, carrying out interface definition A101, and recording interface basic information, wherein the basic information comprises an interface address, a request type, a parameter type and the like.
S202, performing interface setting A102, and configuring a request message field.
The configuration request message field comprises the configuration of the fetch number aiming at each request message field.
S30, verifying the interface, checking whether the interface configuration meets the requirements, and recording an operation log.
S30, verifying the interface, checking whether the interface configuration meets the requirement, and recording an operation log, wherein the step comprises the following steps:
s301, judging whether a field is nested with A103;
if A103 judges yes, carrying out parameter configuration A104;
if the A103 judges no, judging whether the current interface has a front interface or simply writes back the A109;
it should be noted that, whether the current interface has a front interface or a simple write-back a109 is determined, so that other interfaces are executed before the current interface is executed, for example, a token needs to be acquired first; or after the current interface is successfully executed, simply write back the data, for example, a certain value in the return message is needed.
If A109 judges yes, interface bus configuration A110 is carried out; the interface bus configuration A110 comprises a configuration before the current interface is executed and a configuration after the current interface is successfully executed; and judging whether the return message A111 needs to be analyzed, namely whether the interface return message needs to be converted into the form field information, and storing and displaying.
If the A109 judges no, judging whether the return message A111 needs to be analyzed or not;
if A111 judges yes, then the analysis interface is set to A112, namely the returned message field is matched with the database field one by one, and the two types are divided into an object and an array.
If A111 judges no, then carry out interface content verification A123, namely according to the configuration information, get the request message.
It is determined whether or not the requirement a124 is met.
If A124 determines no, it is necessary to complete the information starting from interface definition A101.
If A124 determines yes, an interface call A125 is made.
S302, recording an interface call log A126.
It should be noted that, after the parsing interface setting a112, the method further includes:
it is determined whether the parameter type is the object a113.
If A113 judges yes, a piece of data of the returned message is fetched and stored.
If the A113 judges that the message is not stored, the returned message data is circularly fetched and stored.
It is determined whether the return message is nested a116, i.e., whether the return message field consists of an object, an array, and has not been further processed.
If A116 judges yes, the analysis parameter is composed into A118, that is, the fields need to be used as separate return message content for analysis, and the analysis parameters are divided into two types of objects and arrays.
If the A116 judges no, the analysis interface verification A117 is performed, namely, the verification is performed by using a return message according to analysis configuration information.
It is determined whether or not the requirement a124 is met.
Note that, after the analysis parameter forms a118, the method further includes:
it is determined whether the analysis parameter type is object a119.
If A119 judges yes, a piece of data in the returned message parameters is taken and stored A120.
If the judgment of A119 is negative, all data in the returned message parameters are taken and stored A121.
Note that if a119 determines no, all data in the parameters of the return message are taken and stored a121, and then the method further includes:
it is determined whether the return message parameter is nested a122, i.e. whether the return message parameter field consists of an object, an array, and has not been further processed.
If A122 determines yes, then parse parameters are taken to form A118, i.e., a recursive reference.
If A122 is negative, it is referenced by parse interface setting A112.
Wherein the parameters constitute configuration a104, comprising:
judging whether the parameter type is an object A105;
if A105 judges yes, a value A106 is taken, namely, a piece of data meeting the condition is taken from the fetch table, and request message field assignment is carried out.
If the A106 judges that the request message is not processed, the A107 is circularly fetched, namely all data meeting the condition are fetched from the fetch table, and the request message field is circularly fetched.
It is determined whether the request parameters in the parameter configuration are nested in a108, i.e. whether the request parameter field is composed of an object, an array, and not yet further processed.
If A108 determines yes, then a parameter configuration A104 is performed, i.e., a recursive reference.
If A108 determines no, it is referenced by the fields in interface setting A102 and then continues to determine if there are more nested fields A103 that have not yet been processed.
It should be noted that, whether the message field is nested with the a103 is determined, and whether the request message field is composed of an object and an array is determined and is not further processed.
It should be noted that, the parameter configuration a104 is performed, and the request message field is further configured to use the message field as a separate request message content, and is divided into two types, namely, an object and an array.
The invention defines the form and the related field information; identifying interface information, carrying out interface configuration, and analyzing the interface configuration; and verifying the interface, checking whether the interface configuration meets the requirement, and recording an operation log. The invention can enable the application personnel to quickly, efficiently and accurately interact data with the heterogeneous software system.
The present invention is to
1. The technical means used include:
SpringBoot、SpringDataJpa、OKHttp、Jquery。
2. an interface definition table comprising:
3. an interface setting table comprising:
4. a parameter composition table comprising:
5. an interface bus table comprising:
6. parsing an interface setting table, comprising:
7. resolving a parameter composition table comprising:
8. a log table comprising:
it should be understood that although described in a certain order, the steps are not necessarily performed sequentially in the order described. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, some steps of the present embodiment may include a plurality of steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily sequential, but may be performed alternately or alternately with at least a part of the steps or stages in other steps or other steps.
In one embodiment, referring to fig. 3, a software heterogeneous system is further provided in an embodiment of the present invention, and the data interaction adaptive method of the software heterogeneous system is applied to the system.
In one embodiment, a computer device is also provided in an embodiment of the present invention, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory communicate with each other via the communication bus.
A memory for storing a computer program;
and the processor is used for executing the software heterogeneous system data interaction self-adaption method when executing the computer program stored in the memory, and the steps in the method embodiment are realized when the processor executes the instructions.
The communication bus mentioned by the above terminal may be a peripheral component interconnect standard (Peripheral ComponentInterconnect, abbreviated as PCI) bus or an extended industry standard architecture (Extended Industry StandardArchitecture, abbreviated as EISA) bus, etc. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface is used for communication between the terminal and other devices.
The memory may include random access memory (Random Access Memory, RAM) or non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application SpecificIntegrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
The computer device includes a user device and a network device. Wherein the user equipment includes, but is not limited to, a computer, a smart phone, a PDA, etc.; the network device includes, but is not limited to, a single network server, a server group of multiple network servers, or a Cloud based Cloud Computing (Cloud Computing) consisting of a large number of computers or network servers, where Cloud Computing is one of distributed Computing, and is a super virtual computer consisting of a group of loosely coupled computer sets. The computer device can be used for realizing the invention by running alone, and can also be accessed into a network and realized by interaction with other computer devices in the network. Wherein the network where the computer device is located includes, but is not limited to, the internet, a wide area network, a metropolitan area network, a local area network, a VPN network, and the like.
It should also be understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
In one embodiment of the invention there is also provided a storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method embodiments described above.
Those skilled in the art will appreciate that implementing all or part of the above described embodiment methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the above described embodiment methods. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory.
It should be understood that as used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items. The foregoing embodiment of the present invention has been disclosed with reference to the number of embodiments for the purpose of description only, and does not represent the advantages or disadvantages of the embodiments.
Those of ordinary skill in the art will appreciate that: the above discussion of any embodiment is merely exemplary and is not intended to imply that the scope of the disclosure of embodiments of the invention, including the claims, is limited to such examples; combinations of features of the above embodiments or in different embodiments are also possible within the idea of an embodiment of the invention, and many other variations of the different aspects of the embodiments of the invention as described above exist, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. of the embodiments should be included in the protection scope of the embodiments of the present invention.

Claims (10)

1. The data interaction self-adaption method of the software heterogeneous system is characterized by comprising the following steps of:
s10, defining a form and related field information;
s20, identifying interface information, carrying out interface configuration, and analyzing the interface configuration;
s30, verifying the interface, checking whether the interface configuration meets the requirements, and recording an operation log.
2. The method for data interaction adaptation of a heterogeneous software system according to claim 1, wherein the identifying interface information, performing interface configuration, and analyzing interface configuration comprises:
identifying interface information, carrying out interface definition A101, and recording interface basic information, wherein the basic information comprises an interface address, a request type, a parameter type and the like;
interface setting A102 is performed to configure the request message field.
3. The software heterogeneous system data interaction adaptive method according to claim 2, wherein the configuring request message fields includes performing a fetch configuration for each request message field.
4. The software heterogeneous system data interaction adaptive method according to claim 1, wherein the step of S30 verifying the interface, checking whether the interface configuration meets the requirements, and recording the operation log comprises:
s301, judging whether a field is nested with A103;
if A103 judges yes, carrying out parameter configuration A104;
if the A103 judges no, judging whether the current interface has a front interface or simply writes back the A109;
if A109 judges yes, interface bus configuration A110 is carried out; the interface bus configuration A110 comprises a configuration before the current interface is executed and a configuration after the current interface is successfully executed; judging whether the return message A111 needs to be analyzed, namely whether the interface return message needs to be converted into form field information, and storing and displaying;
if the A109 judges no, judging whether the return message A111 needs to be analyzed or not;
if A111 judges yes, then the analysis interface is set to A112, namely the returned message field is matched with the database field one by one, and the two types are divided into an object and an array;
if the A111 judges that the interface is not the interface, the interface content verification A123 is carried out, namely, a request message is obtained according to the configuration information;
judging whether the requirements A124 are met;
if the A124 judges that the interface is not defined, the information is perfected from the interface definition A101;
if A124 judges yes, make interface call A125;
s302, recording an interface call log A126.
5. The software heterogeneous system data interaction adaptation method according to claim 4, wherein the parameters constitute configuration a104, comprising:
judging whether the parameter type is an object A105;
if A105 judges yes, a value A106 is taken, namely a piece of data meeting the condition is taken from the fetch table, and request message field assignment is carried out;
if the A106 judges that the request message is not processed, the A107 is circularly fetched, namely all data meeting the condition are fetched from the fetch table, and the request message field is circularly fetched;
judging whether the request parameters in the parameter composition are nested with A108, namely whether the request parameter field consists of an object and an array and is not further processed;
if A108 judges yes, then parameter constitution configuration A104 is carried out, namely recursion reference is carried out;
if A108 determines no, it is referenced by the fields in interface setting A102 and then continues to determine if there are more nested fields A103 that have not yet been processed.
6. The software heterogeneous system data interaction adaptation method according to claim 5, wherein after the parsing interface is set to a112, further comprising:
judging whether the parameter type is an object A113;
if the A113 judges that the message is the return message, taking and storing a piece of data;
if the A113 judges that the message is not the data, circularly taking the returned message data for storage;
judging whether the return message is nested with A116, namely whether the return message field consists of an object and an array and is not further processed;
if A116 judges yes, then analyzing parameter to form A118, namely analyzing the field as the independent return message content, and dividing the field into two types of object and array;
if the A116 judges no, the analysis interface verification A117 is carried out, namely, the verification is carried out by using a return message according to analysis configuration information;
it is determined whether or not the requirement a124 is met.
7. The software heterogeneous system data interaction adaptation method according to claim 6, wherein after the parsing parameters form a118, further comprising:
judging whether the analysis parameter type is an object A119;
if A119 judges yes, a piece of data in the returned message parameters is taken and stored A120;
if the judgment of A119 is negative, all data in the returned message parameters are taken and stored A121.
8. The method for adapting data interaction of a heterogeneous software system according to claim 7, wherein if a119 judges no, then taking all data in the parameters of the returned message to store a121, and further comprising:
judging whether the return message parameter is nested with A122, namely whether the return message parameter field consists of an object and an array and is not further processed;
if A122 is judged to be yes, then resolving parameter construction A118 is carried out, namely recursive reference is carried out;
if A122 is negative, it is referenced by parse interface setting A112.
9. A computer device comprising a memory storing a computer program and a processor implementing the steps of the software heterogeneous system data interaction adaptation method of any of claims 1-8 when the computer program is loaded and executed.
10. A storage medium storing a computer program which, when loaded and executed by a processor, implements the steps of the software heterogeneous system data interaction adaptation method of any of claims 1-8.
CN202311470468.2A 2023-11-07 2023-11-07 Data interaction self-adaption method for heterogeneous software system Pending CN117331600A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311470468.2A CN117331600A (en) 2023-11-07 2023-11-07 Data interaction self-adaption method for heterogeneous software system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311470468.2A CN117331600A (en) 2023-11-07 2023-11-07 Data interaction self-adaption method for heterogeneous software system

Publications (1)

Publication Number Publication Date
CN117331600A true CN117331600A (en) 2024-01-02

Family

ID=89275702

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311470468.2A Pending CN117331600A (en) 2023-11-07 2023-11-07 Data interaction self-adaption method for heterogeneous software system

Country Status (1)

Country Link
CN (1) CN117331600A (en)

Similar Documents

Publication Publication Date Title
CN110489417B (en) Data processing method and related equipment
US9612867B2 (en) Apparatus and method for data partition and allocation in heterogeneous multi-processor environment
CN107480260B (en) Big data real-time analysis method and device, computing equipment and computer storage medium
CN112506950A (en) Data aggregation processing method, computing node, computing cluster and storage medium
CN109345081B (en) Data acquisition method and device and electronic equipment
CN107784195A (en) Data processing method and device
CN106649584B (en) Index processing method and device in master-slave database system
CN111885184A (en) Method and device for processing hot spot access keywords in high concurrency scene
CN117331600A (en) Data interaction self-adaption method for heterogeneous software system
CN113886199B (en) Data processing method and device
CN110175182B (en) Data checking method and device
CN109918277A (en) Electronic device, the evaluation method of system log cluster analysis result and storage medium
CN111290868B (en) Task processing method, device and system and flow engine
CN109150993B (en) Method for obtaining network request tangent plane, terminal device and storage medium
WO2021143199A1 (en) Method and apparatus for searching log, computer device, and storage medium
CN111353766A (en) Service process processing system and method of distributed service system
US9235382B2 (en) Input filters and filter-driven input processing
CN113076178B (en) Message storage method, device and equipment
CN114817311B (en) Parallel computing method applied to GaussDB database storage process
CN112698715B (en) Execution control method, device, embedded system, equipment and medium
CN116610455B (en) Resource constraint description system and method of programmable network element equipment
CN110209512B (en) Data checking method and device based on multiple data sources
CN109886327B (en) System and method for processing Java data in distributed system
CN110990648A (en) Virus query method, server and computer readable storage medium
CN113535783A (en) Streaming data processing method, system, computer device and readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination