CN110895544B - Interface data processing method, device, system and storage medium - Google Patents
Interface data processing method, device, system and storage medium Download PDFInfo
- Publication number
- CN110895544B CN110895544B CN201810971420.2A CN201810971420A CN110895544B CN 110895544 B CN110895544 B CN 110895544B CN 201810971420 A CN201810971420 A CN 201810971420A CN 110895544 B CN110895544 B CN 110895544B
- Authority
- CN
- China
- Prior art keywords
- query
- interface
- service module
- target
- data
- 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.)
- Active
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an interface data processing method, a device, a system and a storage medium, wherein the interface data processing method is characterized in that a service module is defined in advance, and attribute information of an interface is configured, wherein the attribute information at least comprises a label of the service module contained in the interface. And then splitting the interface to be configured into a plurality of target service modules according to the attribute information, and acquiring query data of the target service modules one by one based on the query dependency relationship among the plurality of target service modules. Therefore, compared with the prior art, the scheme can save the data query time of the same target service module in a plurality of interfaces, and further improve the data processing efficiency of the interfaces.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method, an apparatus, a system, and a storage medium for processing interface data.
Background
An API (Application Programming Interface) is a predefined function that is intended to provide applications and developers the ability to access a set of routines based on certain software or hardware, without having to access source code or understand the details of internal workings.
Generally, a service system providing an interface service to the outside includes a huge number of interfaces. The interface is required to be programmed one by developers, the complexity of interface development is high, and great manpower is required to be consumed.
Therefore, how to provide an interface data processing method capable of improving the data processing efficiency of the interface becomes a major technical problem to be solved by those skilled in the art.
Disclosure of Invention
In view of the above problems, the present invention has been made to provide a solution that overcomes or at least partially solves the above problems:
an interface data processing method, predefining a service module and configuring attribute information of an interface, where the attribute information at least includes a label of the service module included in the interface, includes:
acquiring attribute information of an interface to be configured;
splitting the interface to be configured according to the attribute information to obtain a target service module;
and acquiring query data of the target business module based on the query dependency relationship among the target business modules.
An interface data processing device, predefining a service module and configuring attribute information of an interface, where the attribute information at least includes a tag of the service module included in the interface, and the interface data processing device includes:
the first acquisition module is used for acquiring the attribute information of the interface to be configured;
the splitting module is used for splitting the interface to be configured according to the attribute information to obtain a target service module;
and the second acquisition module is used for acquiring the query data of the target business module based on the query dependency relationship among the target business modules.
An interface data processing system comprising:
a memory for storing a program;
and the processor is used for executing the program, and the program executes any one of the interface data processing methods when running.
A storage medium storing a program which, when executed by a processor, implements any one of the above-described interface data processing methods.
By means of the technical scheme, the invention provides an interface data processing method, which is characterized in that a service module is defined in advance, and attribute information of an interface is configured, wherein the attribute information at least comprises a label of the service module contained in the interface. And then splitting the interface to be configured into a plurality of target service modules according to the attribute information, and acquiring query data of the target service modules one by one based on the query dependency relationship among the plurality of target service modules. In the scheme, when data query is performed on a plurality of interfaces, the same target service module in the interface only needs to perform data query once, and compared with the prior art, the data query time of the same target service module in a plurality of interfaces can be saved, so that the data processing efficiency of the interfaces is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various additional advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a schematic flowchart illustrating an interface data processing method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart illustrating an interface data processing method according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating query dependencies among a plurality of target business modules according to an embodiment of the present invention;
fig. 4 is a schematic flowchart illustrating an interface data processing method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an interface data processing apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an interface data processing apparatus according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The inventor considers that: in a huge number of interfaces included in a service system that provides an interface service to the outside, many interfaces have the same service module except for different specific service logics, and therefore, an embodiment of the present invention provides an interface data processing method, as shown in fig. 1, a service module is defined in advance, and attribute information of an interface is configured, where the attribute information at least includes a tag of the service module included in the interface.
The interface data processing method comprises the following steps:
s11, acquiring attribute information of an interface to be configured;
in the interface data processing system provided in this embodiment, the attribute information of each interface is configured in advance, for example, the attribute information may include a label of a service module included in the interface, may also include database information of a query corresponding to the service module, or may also include call information of a third-party service related to the interface, or a query dependency relationship between different service modules. Besides, the attribute information of the interface can be set by developers according to different service requirements.
Schematically, it is assumed that the preconfigured interface a includes a service module (1), a service module (2), and a service module (3), the interface B includes the service module (1) and the service module (2), and the interface C includes the service module (2) and the service module (3). Meanwhile, labels of the service module (1), the service module (2) and the service module (3) are defined as the label (1), the label (2) and the label (3), respectively. It should be noted that the service module is the smallest query unit in the interface query, and query of an interface can be performed by querying a plurality of service modules included in the interface, and then combining query data of each service module to obtain query data of the interface.
In addition, different service modules may have different data query paths and different data formats, and different query relationships exist between different service modules, for example, query orders are different, that is, query priorities of each service module are different, or a query of a certain service module needs to be based on a query result of another service module. For example, the data format of the service module (1) is SQL, the data format of the service module (2) is CQ, the data format of the service module (3) is JSON, and the like. For another example, the data in the SQL format may be acquired through the database a and the database C, the data in the CQ format may be acquired through the database B, and the data in the JSON format may be acquired through the database C and the database D. For another example, the query priority of the service module is service module (3) > service module (1) = service module (2) in sequence, wherein a single interface query mode is used between the service module (1) and the service module (2), that is, the service module and the service module can query simultaneously.
And then establishing an association relation for the configured interface attributes, as shown in table 1 below, and recording the association relation in a configuration database.
TABLE 1
In this step, attribute information of the interface to be configured is obtained, that is, if the interface to be configured is assumed to be interface a, the attribute information of interface a is obtained in this step, for example: the interface A comprises a business module (1), a business module (2) and a business module (3), the label of the business module (1) is the label (1), the data format of the business module (1) is SQL, and the business module (1) can be inquired in a corresponding database A and a database C.
S12, splitting the interface to be configured according to the attribute information to obtain a target service module;
in this embodiment, the interface to be configured is split into a plurality of service modules by combining the attribute information of the interface, and the split service module is determined as a target service module. It should be noted that the service module included in the interface to be configured may be divided into a basic service module and a specific service module according to different types of the service module, where the interface data processing system provided in this embodiment is based on the basic service module, that is, the basic service module in the service module after the interface is split is determined as a target service module, and then the target service module is subjected to automatic data query, and the automatically queried data is integrated. And the specific service module needs a developer to perform data query.
In other words, the interface can be split into which query blocks, which are determined according to the attribute information of the interface, where the attribute information includes the label of the target service module.
Specifically, as shown in fig. 2, this embodiment provides a specific implementation step of splitting the interface to be configured according to the attribute information to obtain a target service module, where the specific implementation step includes:
s21, determining the label contained in the attribute information of the interface to be configured as a target label,
s22, determining the business module corresponding to the target label as the target business module.
For example, if the interface a can be split into the target service module 3, the target service module 1, and the target service module 5, the attribute information of the interface a needs to be configured in advance as the tags 3, 1, and 5, and similarly, if the interface B can be split into the target service module 3, the target service module 1, and the target service module 2, the attribute information of the interface B needs to be configured in advance as the tags 3, 1, and 2.
When data query needs to be performed on the interface a and the interface B, it is first determined that the target tags are tag 3, tag 1, tag 5, and tag 2, and then it is determined that the service module corresponding to the above tags is the target service module, that is, it is determined that the service module 3, the service module 1, the service module 5, and the service module 2 are the target service modules.
Then, data query is performed on the target service module, it should be noted that, in this embodiment, the same target service module only needs to perform data query once, that is, the target service module 3 and the target service module 1 in the interface a only perform data query once respectively. However, in the prior art, the interface a and the interface B need to be queried separately, and at this time, the target service module 3 and the target service module 1 need to be queried twice. Therefore, according to the scheme, a plurality of interfaces are split, a general basic service module (target service module) in the interfaces is subjected to system automatic query, the query time of the target service module 3 and the target service module 1 is saved, and a special service module is subjected to manual query. Because one project usually needs to query data of thousands of interfaces, the scheme can save the repeated query time of a plurality of same target service modules, reduce the workload of developers for querying a large number of basic service modules and further improve the data processing efficiency of the interfaces.
Further, the present embodiment provides a process flow for performing an automated query on a target service module, which includes:
and S13, acquiring query data of the target service modules based on the query dependency relationship among the target service modules.
In this embodiment, a query tag of each service module is defined, then, when interface attribute information is configured, a query dependency relationship among a plurality of service modules is established, and it is assumed that the defined query dependency relationship includes three types, as shown in fig. 3, a first type is a single-interface query, a second type is a multiple-time parallel query, and a third type is an interface nested query.
Specifically, the query with a single interface, that is, the query sequence among the plurality of service modules is not required to be limited, and the result query may be performed on the plurality of service modules in any sequence, for example, when the query dependency is a query with a single interface, the target service module may be queried one by one.
The query sequence of the plurality of service modules is concurrent and needs to be queried in parallel, and then query results of the plurality of service modules are integrated.
The interface nesting query is that the query sequence of a plurality of service modules is sequentially carried out, the query of the next service module needs to depend on the query result of the previous service module as input, and then the query result of the last service module is determined as the result of the interface nesting query.
It should be noted that no matter which query dependency relationship exists among a plurality of business modules, the business module is used as the smallest query unit, and the data query flows are the same, as shown in fig. 4, including the steps of:
s41, converting the data format of the target service module into a data format to be queried based on the queried database information corresponding to the service module;
and S42, acquiring the query result of the target service module in the database corresponding to the data format to be queried.
Schematically, in this embodiment, the interface formats of the input interface data processing system are all CQ, then the interface is split and divided into the service module (1) and the service module (2), then, from the database information of the query corresponding to the predefined service module, it is determined that the data format of the service module (1) to be queried is SQL, data query needs to be performed in the database a or the database C, and a corresponding query result is obtained.
After the query result of each target service module is obtained, the target query data of the interface to be configured is determined based on the query data of the target service module and the query dependency relationship.
Specifically, in this embodiment, when the query dependency relationship is a single interface query, it is determined that the query data of the target service module are all target query data of the interface to be configured;
when the query dependency relationship is a plurality of times of parallel queries, determining the combined data of the query data of the target service module as the target query data of the interface to be configured;
and when the query dependency relationship is interface nesting query, determining the query data of the last target service module as the target query data of the interface to be configured.
Therefore, compared with the prior art, the data query time of the same target service module in the plurality of interfaces can be saved, and the data processing efficiency of the interfaces is improved.
In addition, on the basis of the above embodiments, corresponding to the above method, an embodiment of the present invention further provides an interface data processing apparatus, please refer to fig. 5, which shows a schematic structural diagram of the interface data processing apparatus, and the interface data processing apparatus includes:
a first obtaining module 51, configured to obtain attribute information of an interface to be configured;
the splitting module 52 is configured to split the interface to be configured according to the attribute information, so as to obtain a target service module;
a second obtaining module 53, configured to obtain query data of the target service module based on a query dependency relationship among the plurality of target service modules.
Optionally, as shown in fig. 6, the interface data processing apparatus provided in this embodiment further includes:
a determining module 61, configured to determine, based on the query data of the target service module and the query dependency, target query data of the interface to be configured.
In addition, the present embodiment also provides a processor and a memory, where the first obtaining module, the splitting module, the second obtaining module, the determining module, and the like are all stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions.
The processor comprises a kernel, and the kernel calls the corresponding program unit from the memory. The kernel can be set to be one or more than one, when data query is carried out on a plurality of interfaces, the same target service module in the interfaces only needs to carry out data query once, compared with the prior art, the data query time of the same target service module in a plurality of interfaces can be saved, and the data processing efficiency of the interfaces is further improved.
The memory may include volatile memory in a computer readable medium, random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
An embodiment of the present invention provides a storage medium on which a program is stored, the program implementing the interface data processing method when executed by a processor.
The embodiment of the invention provides a processor, which is used for running a program, wherein the interface data processing method is executed when the program runs.
The embodiment of the invention provides equipment, which comprises a processor, a memory and a program which is stored on the memory and can run on the processor, wherein the processor executes the program and realizes the following steps:
predefining a service module and configuring attribute information of an interface, wherein the attribute information at least comprises a label of the service module contained in the interface, and the interface data processing method comprises the following steps:
acquiring attribute information of an interface to be configured;
splitting the interface to be configured according to the attribute information to obtain a target service module;
and acquiring query data of the target business module based on the query dependency relationship among the target business modules.
Optionally, the method further includes:
and determining the target query data of the interface to be configured based on the query data of the target service module and the query dependency relationship.
Optionally, the splitting the interface to be configured according to the attribute information to obtain a target service module includes:
determining the label contained in the attribute information of the interface to be configured as a target label,
and determining the business module corresponding to the target label as the target business module.
Optionally, the acquiring query data of the target service module includes:
converting the data format of the target service module into a data format to be queried based on query database information corresponding to the service module;
and acquiring the query data of the target service module in the query database corresponding to the data format to be queried.
Optionally, the obtaining query data of the target service module based on the query dependency relationship among the plurality of target service modules includes:
when the query dependency relationship is a single interface query, querying the target service modules one by one;
when the query dependency relationship is a plurality of times of parallel queries, the target service module is queried in parallel;
and when the query dependency relationship is interface nested query, taking the query result of the previous service module as the query input information of the next service module.
Optionally, the determining the target query data of the interface to be configured based on the query data of the target service module and the query dependency relationship includes:
when the query dependency relationship is a single interface query, determining that the query data of the target service module are the target query data of the interface to be configured;
when the query dependency relationship is a plurality of times of parallel queries, determining the combined data of the query data of the target service module as the target query data of the interface to be configured;
and when the query dependency relationship is interface nesting query, determining the query data of the last target service module as the target query data of the interface to be configured.
The device herein may be a server, a PC, a PAD, a mobile phone, etc.
The present application further provides a computer program product adapted to perform a program for initializing the following method steps when executed on a data processing device:
predefining a service module and configuring attribute information of an interface, wherein the attribute information at least comprises a label of the service module contained in the interface, and the interface data processing method comprises the following steps:
acquiring attribute information of an interface to be configured;
splitting the interface to be configured according to the attribute information to obtain a target service module;
and acquiring query data of the target business modules based on the query dependency relationship among the target business modules.
Optionally, the method further includes:
and determining the target query data of the interface to be configured based on the query data of the target service module and the query dependency relationship.
Optionally, the splitting the interface to be configured according to the attribute information to obtain a target service module includes:
determining the label contained in the attribute information of the interface to be configured as a target label,
and determining the business module corresponding to the target label as the target business module.
Optionally, the acquiring query data of the target service module includes:
converting the data format of the target service module into a data format to be queried based on query database information corresponding to the service module;
and acquiring the query data of the target service module in the query database corresponding to the data format to be queried.
Optionally, the obtaining query data of the target service module based on the query dependency relationship among the plurality of target service modules includes:
when the query dependency relationship is a single interface query, querying the target service modules one by one;
when the query dependency relationship is a plurality of times of parallel queries, the target service module is queried in parallel;
and when the query dependency relationship is interface nested query, taking the query result of the previous service module as the query input information of the next service module.
Optionally, the determining the target query data of the interface to be configured based on the query data of the target service module and the query dependency relationship includes:
when the query dependency relationship is a single interface query, determining that the query data of the target service module are all the target query data of the interface to be configured;
when the query dependency relationship is a plurality of times of parallel queries, determining the combined data of the query data of the target service module as the target query data of the interface to be configured;
and when the query dependency relationship is interface nesting query, determining the query data of the last target service module as the target query data of the interface to be configured.
In summary, the present invention provides an interface data processing method, an apparatus, a system, and a storage medium, where the interface data processing method configures attribute information of an interface by predefining a service module, where the attribute information at least includes a tag of the service module included in the interface. And then splitting the interface to be configured into a plurality of target service modules according to the attribute information, and acquiring query data of the target service modules one by one based on the query dependency relationship among the plurality of target service modules. Therefore, compared with the prior art, the data query time of the same target service module in the interfaces can be saved, and the data processing efficiency of the interfaces is improved.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (8)
1. An interface data processing method is characterized in that a service module is predefined, and attribute information of an interface is configured, wherein the attribute information at least comprises a label of the service module contained in the interface, and the interface data processing method comprises the following steps:
acquiring attribute information of an interface to be configured;
splitting the interface to be configured according to the attribute information to obtain a target service module;
acquiring query data of the target business modules based on query dependency relations among the target business modules;
the splitting the interface to be configured according to the attribute information to obtain a target service module includes:
determining the label contained in the attribute information of the interface to be configured as a target label,
determining the service module corresponding to the target label as the target service module;
the obtaining query data of the target service module based on the query dependency relationship among the plurality of target service modules includes:
when the query dependency relationship is a single interface query, querying the target service modules one by one;
when the query dependency relationship is a plurality of times of parallel queries, the target service module is queried in parallel;
and when the query dependency relationship is interface nested query, taking the query result of the previous service module as the query input information of the next service module.
2. The interface data processing method according to claim 1, further comprising:
and determining the target query data of the interface to be configured based on the query data of the target service module and the query dependency relationship.
3. The interface data processing method according to claim 1, wherein the acquiring query data of the target service module includes:
converting the data format of the target service module into a data format to be queried based on query database information corresponding to the service module;
and acquiring the query data of the target service module in the query database corresponding to the data format to be queried.
4. The interface data processing method according to claim 2, wherein the determining target query data of the interface to be configured based on the query data of the target service module and the query dependency relationship includes:
when the query dependency relationship is a single interface query, determining that the query data of the target service module are the target query data of the interface to be configured;
when the query dependency relationship is a plurality of times of parallel queries, determining the combined data of the query data of the target service module as the target query data of the interface to be configured;
and when the query dependency relationship is interface nesting query, determining the query data of the last target service module as the target query data of the interface to be configured.
5. An interface data processing device, characterized in that, a service module is predefined, and attribute information of an interface is configured, the attribute information at least includes a label of the service module included in the interface, the interface data processing device includes:
the first acquisition module is used for acquiring the attribute information of the interface to be configured;
the splitting module is used for splitting the interface to be configured according to the attribute information to obtain a target service module;
the second acquisition module is used for acquiring query data of the target business modules based on query dependency relations among the target business modules;
the splitting module splits the interface to be configured according to the attribute information to obtain a target service module, including:
determining the label contained in the attribute information of the interface to be configured as a target label,
determining the service module corresponding to the target label as the target service module;
the second obtaining module obtains query data of the target service module based on the query dependency relationship among the plurality of target service modules, and the query data includes:
when the query dependency relationship is a single interface query, querying the target service modules one by one;
when the query dependency relationship is a plurality of times of parallel queries, the target service module is queried in parallel;
and when the query dependency relationship is interface nesting query, taking the query result of the previous service module as the query input information of the next service module.
6. The interface data processing apparatus according to claim 5, further comprising:
and the determining module is used for determining the target query data of the interface to be configured based on the query data of the target service module and the query dependency relationship.
7. An interface data processing system, comprising:
a memory for storing a program;
a processor for executing the program, the program when running executing the interface data processing method of any one of claims 1 to 4.
8. A storage medium characterized by storing a program which, when executed by a processor, implements the interface data processing method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810971420.2A CN110895544B (en) | 2018-08-24 | 2018-08-24 | Interface data processing method, device, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810971420.2A CN110895544B (en) | 2018-08-24 | 2018-08-24 | Interface data processing method, device, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110895544A CN110895544A (en) | 2020-03-20 |
| CN110895544B true CN110895544B (en) | 2023-02-21 |
Family
ID=69784736
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810971420.2A Active CN110895544B (en) | 2018-08-24 | 2018-08-24 | Interface data processing method, device, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110895544B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111506440B (en) * | 2020-04-14 | 2022-11-04 | 上海春魁信息技术有限公司 | Data processing method, device, equipment and storage medium |
| CN112839083B (en) * | 2020-12-30 | 2022-07-12 | 北京天融信网络安全技术有限公司 | Data transmission method and device and readable storage medium |
| CN113885959B (en) * | 2021-09-30 | 2024-05-14 | 平安银行股份有限公司 | Data processing method, device, equipment and medium based on interface configuration |
| CN113934418A (en) * | 2021-10-19 | 2022-01-14 | 中国银行股份有限公司 | Configuration method and device of atomic program |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653575A (en) * | 2015-12-04 | 2016-06-08 | 重庆川仪自动化股份有限公司 | Data checking method and reporting system employed by same |
| CN105912624A (en) * | 2016-04-07 | 2016-08-31 | 北京中安智达科技有限公司 | Query method for distributed deployed heterogeneous database |
| CN108090154A (en) * | 2017-12-08 | 2018-05-29 | 广州市申迪计算机***有限公司 | A kind of isomerous multi-source data fusion querying method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080065591A1 (en) * | 2006-09-08 | 2008-03-13 | Leon Guzenda | Configurable software database parallel query system and method |
-
2018
- 2018-08-24 CN CN201810971420.2A patent/CN110895544B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653575A (en) * | 2015-12-04 | 2016-06-08 | 重庆川仪自动化股份有限公司 | Data checking method and reporting system employed by same |
| CN105912624A (en) * | 2016-04-07 | 2016-08-31 | 北京中安智达科技有限公司 | Query method for distributed deployed heterogeneous database |
| CN108090154A (en) * | 2017-12-08 | 2018-05-29 | 广州市申迪计算机***有限公司 | A kind of isomerous multi-source data fusion querying method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110895544A (en) | 2020-03-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110895544B (en) | Interface data processing method, device, system and storage medium | |
| EP3353672B1 (en) | Method and apparatus for transferring data between databases | |
| CN110188100A (en) | Data processing method, device and computer storage medium | |
| CN106648839B (en) | Data processing method and device | |
| CN110765151A (en) | Calculation formula processing method and device | |
| US20120159515A1 (en) | Sharing object representations | |
| CN108874379B (en) | Page processing method and device | |
| CN106648567B (en) | Data acquisition method and device | |
| CN114297204A (en) | Data storage and retrieval method and device for heterogeneous data source | |
| CN105447040B (en) | Binary file management and updating method, device and system | |
| CN110837446A (en) | Equipment management method and device applied to embedded system, medium and embedded equipment | |
| CN109977317B (en) | Data query method and device | |
| US11262986B2 (en) | Automatic software generation for computer systems | |
| CN110928941A (en) | Data fragment extraction method and device | |
| CN110019357B (en) | Database query script generation method and device | |
| CN111078905A (en) | Data processing method, device, medium and equipment | |
| CN108241622B (en) | Query script generation method and device | |
| CN114253845A (en) | Automatic testing method and device for special-shaped architecture integration system | |
| CN114138745A (en) | Data integration method and device, storage medium and processor | |
| CN109299125B (en) | Database updating method and device | |
| CN112559444A (en) | SQL (structured query language) file migration method and device, storage medium and equipment | |
| CN108062329B (en) | Data import method and device | |
| CN113282631A (en) | Method and equipment for determining target user based on user portrait data | |
| CN111047415A (en) | Clothing accessory order processing method, system, electronic equipment and storage medium | |
| CN113222084B (en) | Block chain-based date labeling and querying method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |