CN113111111A - Multi-data source database access method - Google Patents
Multi-data source database access method Download PDFInfo
- Publication number
- CN113111111A CN113111111A CN202110368434.7A CN202110368434A CN113111111A CN 113111111 A CN113111111 A CN 113111111A CN 202110368434 A CN202110368434 A CN 202110368434A CN 113111111 A CN113111111 A CN 113111111A
- Authority
- CN
- China
- Prior art keywords
- data
- database
- access
- accessed
- designer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
Abstract
The invention discloses a method, a device, equipment and a storage medium for accessing a multi-data source database, wherein the method comprises the steps of acquiring data to be accessed of the database to construct a designer and an actuator so as to enable the designer and the actuator to meet the requirements of data increment of the database and the access of a data table; configuring access information and processing information according to the data to be accessed by using a designer corresponding to a database; and performing data reading, data processing and data writing on the data to be accessed in the database according to the configuration access information and the processing information by using an actuator corresponding to the database. The invention is realized by adopting a mode of separating a designer from an actuator, separating data acquisition from data storage and adding Kafka message middleware. The method aims to solve the technical problems that in the prior art, when the number of service scenes is large, the types of data sources are unknown, and the data volume possibly changes repeatedly during data access, the data access efficiency is low and cannot be well solved.
Description
Technical Field
The invention relates to the technical field of databases, in particular to a method, a device, equipment and a storage medium for accessing multiple data source databases.
Background
Currently, when data is transferred from a source database to a destination database for storage or calculation, a data access tool is used for the transfer. When multiple source databases are used, multiple access tools are needed to access data in the multiple source databases to the target database.
In the conventional technology, when a target database accesses data from different source databases, different access tools can be selected to access the data respectively according to the different databases and the real-time or offline condition. For example: data in databases such as Mysql, Oracle and the like can be accessed offline by using data access tools such as DataX, Sqoop and the like; real-time incremental data and the like can be accessed by using a data access tool such as Canal and the like.
However, when accessing data, the data access method has many service scenarios and unknown data source types, and in addition, there may be a situation that the data amount changes repeatedly during data access, and a user is very familiar with configuration information of each access tool, which has a high requirement for professional knowledge of the user, and the user operation experience is not good.
Chinese patent publication No. CN109669977A discloses a method, an apparatus, a computer device, and a storage medium for data access across databases, but the technical solution of the patent still cannot be solved well when there are many service scenarios, the types of data sources are unknown, and there may be situations such as repeated changes in data amount during data access.
Therefore, how to improve the user operation experience of data access with multiple data sources and repeatedly changing data amount is a technical problem which needs to be solved urgently.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a method, a device, equipment and a storage medium for accessing a multi-data source database, and aims to solve the technical problems that in the prior art, when the service scenes are more, the types of data sources are unknown, the data quantity possibly changes repeatedly during data access and the like, the data access efficiency is low, and the data access efficiency cannot be well solved.
In order to achieve the above object, the present invention provides a method for accessing multiple data source databases, which comprises the following steps:
acquiring data to be accessed of a database, and constructing a designer and an actuator corresponding to the database according to the database so as to enable the designer and the actuator to meet the data increment of the database and the access of a data table;
configuring access information and processing information according to the data to be accessed by using a designer corresponding to the database;
and performing data reading, data processing and data writing on the data to be accessed in the database according to the configuration access information and the processing information by using an actuator corresponding to the database.
Optionally, before the steps of obtaining data to be accessed to a database, and constructing a designer and an executor corresponding to the database according to the database, so that the designer and the executor satisfy the data increment of the database and the access of a data table, the method further includes:
acquiring data to be accessed in a database and identifying the type of the database;
and calling a data type adapter, and converting the data to be accessed in the database into the required data type by using the data type adapter.
Optionally, the step of calling a data type adapter and converting the data to be accessed to the database into the required data type by using the data type adapter specifically includes:
and converting the data to be accessed of the database between any two types of data including Oracle, Wanli open source, DB2, Mysql, Dameng, HBase, Hive or big gold vault by using the data type adapter.
Optionally, the method for accessing the database includes the steps of obtaining data to be accessed of the database, and constructing a designer and an executor corresponding to the database according to the database, so that the designer and the executor satisfy the data increment of the database and the access of a data table, and specifically includes:
constructing a designer used for connecting the interactive equipment so as to enable the designer to receive configuration access information and processing information transmitted by the interactive equipment;
an executor is configured to connect a processor and a memory such that the executor invokes the processor and the memory to perform data access.
Optionally, the step of configuring access information and processing information according to the data to be accessed by using a designer corresponding to the database specifically includes:
configuring data input, data processing and data output modes in the database access process by using a visual configuration interface provided by interactive equipment and through the user-defined dragging of a visual configuration node;
and configuring the corresponding relation between the source data source, the target data source and the source data and the target data by filling in the application form by using an application form entry interface provided by the interactive equipment.
Optionally, the step of performing data reading, data processing, and data writing on the data to be accessed in the database according to the configuration access information and the processing information by using an actuator corresponding to the database specifically includes:
reading and processing access data in batches by adopting a rear end actuator of a visual configuration interface, and outputting the processed data;
adopting a default actuator, quickly accessing data to be accessed through a Kafka message queue and distributed deployment, performing read-write separation, and outputting the processed data;
and processing the customized data in the access data according to the preset logic by adopting the personalized extension actuator, and further packaging and writing the data into the Kafka queue for outputting.
In addition, to achieve the above object, the present invention further provides a multiple data source database access apparatus, where the multiple data source database access apparatus includes:
the system comprises a construction module, a database access module and a data access module, wherein the construction module is used for acquiring data to be accessed of a database, and constructing a designer and an actuator corresponding to the database according to the database so as to enable the designer and the actuator to meet the data increment of the database and the access of a data table;
the configuration module is used for configuring access information and processing information according to the data to be accessed by utilizing a designer corresponding to the database;
and the execution module is used for reading, processing and writing the data to be accessed in the database according to the configuration access information and the processing information by using the actuator corresponding to the database.
In addition, to achieve the above object, the present invention further provides a multiple data source database access device, where the multiple data source database access device includes: the system comprises a memory, a processor and a multi-data-source database access program which is stored on the memory and can run on the processor, wherein when the multi-data-source database access program is executed by the processor, the steps of the multi-data-source database access method are realized.
In addition, in order to achieve the above object, the present invention further provides a storage medium, where the storage medium stores a multiple data source database access program, and when the multiple data source database access program is executed by a processor, the multiple data source database access method performs the steps of the multiple data source database access method as described in any one of the above.
According to the method, a designer and an actuator corresponding to a database are constructed according to the database by acquiring data to be accessed of the database, so that the designer and the actuator meet the requirements of data increment of the database and the access of a data table; on one hand, configuring access information and processing information according to the data to be accessed by using a designer corresponding to the database; and on the other hand, performing data reading, data processing and data writing on the data to be accessed in the database according to the configuration access information and the processing information by using an actuator corresponding to the database. The method provided by the invention is realized by adopting a mode of separating a designer from an actuator, separating data acquisition from data storage and adding Kafka message middleware. The method aims to solve the technical problems that in the prior art, when the number of service scenes is large, the types of data sources are unknown, and the data volume possibly changes repeatedly during data access, the data access efficiency is low and cannot be well solved.
Drawings
Fig. 1 is a flowchart illustrating a multiple data source database access method according to a first embodiment of the present invention.
FIG. 2 is a flow chart illustrating database type conversion according to the present invention.
FIG. 3 is a flow chart illustrating the construction of the designer and executor according to the present invention.
FIG. 4 is a schematic flow chart of designer configuration information according to the present invention.
Fig. 5 is a schematic flow chart of the data access by the executor of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic flow chart of a multiple data source database access method according to a first embodiment of the present invention, and provides the multiple data source database access method according to the first embodiment of the present invention.
In this embodiment, the method for accessing multiple data source databases includes the following steps:
step S10: acquiring data to be accessed of a database, and constructing a designer and an actuator corresponding to the database according to the database so as to enable the designer and the actuator to meet the data increment of the database and the access of a data table;
step S20: configuring access information and processing information according to the data to be accessed by using a designer corresponding to the database;
step S30: and performing data reading, data processing and data writing on the data to be accessed in the database according to the configuration access information and the processing information by using an actuator corresponding to the database.
It should be noted that, with reference to fig. 2, before acquiring data to be accessed to a database, and constructing a designer and an executor corresponding to the database according to the database, so that the designer and the executor satisfy the data increment of the database and the access step of a data table, the method further includes:
step A10: acquiring data to be accessed in a database and identifying the type of the database;
step A20: and calling a data type adapter, and converting the data to be accessed in the database into the required data type by using the data type adapter.
It should be understood that, invoking a data type adapter, and converting the data to be accessed to the database into the required data type by using the data type adapter specifically includes:
and converting the data to be accessed of the database between any two types of data including Oracle, Wanli open source, DB2, Mysql, Dameng, HBase, Hive or big gold vault by using the data type adapter.
It should be noted that, with reference to fig. 3, acquiring data to be accessed by a database, and constructing a designer and an executor corresponding to the database according to the database, so that the designer and the executor satisfy the data increment of the database and the access step of a data table, specifically including:
step S101: the method comprises the steps that a designer used for connecting the interactive device is constructed, so that the designer receives configuration access information and processing information transmitted by the interactive device.
Step S102: an executor is configured to connect a processor and a memory such that the executor invokes the processor and the memory to perform data access.
It should be noted that, with reference to fig. 4, the step of configuring access information and processing information according to the data to be accessed by using a designer corresponding to the database specifically includes:
step S201: and configuring data input, data processing and data output modes in the database access process by utilizing a visual configuration interface provided by interactive equipment and through the user-defined dragging of the visual configuration node.
Step S202: and configuring the corresponding relation between the source data source, the target data source and the source data and the target data by filling in the application form by using an application form entry interface provided by the interactive equipment.
It is to be understood that for the visual configuration interface (Web-ETL):
the WEB-ETL is designed in a process node mode, and one process is formed by combining a plurality of process nodes. Each flow node corresponds to a different component, thereby implementing a corresponding node function.
Each process link has only one specific function, and a plurality of components are connected together to form a chain process. Each process link only concerns the processing process configuration of the node, and only has the relation of input and output contents with the upstream node or the downstream node, so that the user-defined configuration of the whole data process can be achieved through different combinations of the process links. The data processing processes such as complex cleaning, conversion, filtering, screening and the like are completed through three types of nodes of 'input source', 'output source' and 'processing' provided by the platform, the nodes can be customized and expanded, and each node only focuses on the required attributes of the service and the input and output contents.
The data access task created by the Web-ETL (visual configuration) will be processed by the executor of the Web-ETL for data access.
It is to be understood that for an application form entry interface:
the access application form mainly adopts a form filling mode, during configuration, a source data source and a data table/file/interface (input source) are selected, a target data source and a data table (output source) are selected, the corresponding relation of data items of the source data and the target data table is configured, an access processing mode is configured, and a platform automatically generates a corresponding data access task according to the configured content and the processing mode after storage. The access application form does not need to pay attention to the intermediate processing process of data access, and can complete configuration only by determining the corresponding relation between input and output contents and data items.
The data access task created through the access application form can specify the executor to perform data access processing. The platform provides a plurality of actuators such as Web-ETL, default actuator, login authentication actuator, other custom actuator and the like. When the Web-ETL is selected, a Web-ETL flow task is automatically created through an interface provided by the Web-ETL according to the configuration content of the form.
It should be noted that, with reference to fig. 5, performing data reading, data processing, and data writing on the to-be-accessed data of the database according to the configuration access information and the processing information by using an actuator corresponding to the database specifically includes:
step S301: and reading and processing the access data in batches by adopting a rear end actuator of a visual configuration interface, and outputting the processed data.
Step S302: and adopting a default actuator, quickly accessing data to be accessed through a Kafka message queue and distributed deployment, performing read-write separation, and outputting the processed data.
Step S303: and processing the customized data in the access data according to the preset logic by adopting the personalized extension actuator, and further packaging and writing the data into the Kafka queue for outputting.
It is to be understood that for the back end effector of the visual configuration interface:
and the data access task configured through the Web-ETL visual interface and the data access task selecting the Web-ETL in a processing mode when the access application form is configured are processed by a Web-ETL rear-end actuator. And the data access is executed according to the configured flow process.
Each Flow is represented by a Flow class, and each Flow link (e.g., table input and table output) is represented by a FlowLink class. Each FlowLink class records the parameter information required by the component, the component (EtlComponent) it belongs to, and the ID of the next component.
And storing the parameter information in a Json character string mode.
The belonged component indicates which component is adopted by the FlowLink to process, different components have different processing classes to process, and functions are mainly realized in the processing classes. The table input component is used for realizing database connection and reading data from the specified data table; and the file input component is used for realizing the connection of the file server and acquiring and analyzing the file.
The ID of the next component is used to string the FlowLink into a complete Flow. A complete process flow comprises one input source node, N data conversion nodes (N > = 0), one output source node.
The input source node mainly realizes the reading of data. When data is read, the component class acquires data in batches according to the data quantity of the read target table, transmits the data to the next component node after the data is read, and starts to read the next batch of data, so that the problem of memory overflow possibly occurring when the data is acquired at one time in large batch is avoided, and the data processing performance is improved.
The data conversion node mainly implements content processing of data, such as data type conversion (Number- > String, Date- > String … …). When data is converted, the component takes the output content of the previous node as data input, the data is output to the next node after being processed by the service logic of the component, and each type of data conversion node only does the service logic of the node concerned node.
The output source node mainly realizes the storage and the storage of data. And when the data is stored, the component acquires the output content of the previous node, and writes and stores the data into the data table according to the matching relation configured by the nodes and the specified target database.
It is to be understood that for the default actuator:
when the application form is configured, a default executor can be selected for data access.
When data access is carried out, the platform calls a designer to obtain form configuration information and a corresponding executor by taking task scheduling service as a starting point. And if the executor is a default executor, calling the executor and transmitting the application form ID. The actuator executes the following steps:
and acquiring the parameter content configured by the application form according to the ID of the application form.
And connecting the database to obtain access data according to the configuration of the application form.
And packaging the processed data, and writing the data into a Kafka queue, wherein the content comprises a target library address, a target table and data content. One type of database is a TOPIC.
The platform automatically monitors Kafka queue messages, and when new data are written into the queue, the data are stored in the database.
It is to be understood that for the personalized extension enforcer:
some customized data access which cannot be met by the platform can occur in the project landing process, for example, the EXCEL access of a multi-level header and the interface access … … of asymmetric encryption have the main problems that the data source is unknown and the warehousing operation is constant in the data access process, so that the platform supports the customized extension of the third-party service to meet the requirement of the customized data access. The personalized extension executor realizes the following contents:
developed in the form of microservices and supporting automatic registration to the Nacos.
And providing a calling interface, supporting the designer to call and receive the related information of the application form.
Data is obtained from a source data source according to the application form configuration.
And analyzing the data and carrying out structured processing on the data according to the configuration of the application form.
The data is placed in the corresponding Kafka queue.
When data access is carried out, the platform calls a designer to obtain form configuration information and a corresponding executor by taking task scheduling service as a starting point. And if the executor is the personalized extension executor, calling the executor and transmitting the ID of the application form. And the executor processes according to the logic of the executor, and finally writes the packaged data into the Kafka queue. The platform automatically monitors Kafka queue messages, and when new data are written into the queue, the data are stored in the database.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g., a Read Only Memory (ROM)/Random Access Memory (RAM), a magnetic disk, an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the methods according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (9)
1. The multi-data source database access method is characterized by comprising the following steps:
acquiring data to be accessed of a database, and constructing a designer and an actuator corresponding to the database according to the database so as to enable the designer and the actuator to meet the data increment of the database and the access of a data table;
configuring access information and processing information according to the data to be accessed by using a designer corresponding to the database;
and performing data reading, data processing and data writing on the data to be accessed in the database according to the configuration access information and the processing information by using an actuator corresponding to the database.
2. The multiple data source database access method according to claim 1, wherein before the steps of obtaining the data to be accessed from the database, and constructing the designer and the executor corresponding to the database according to the database, so that the designer and the executor satisfy the data increment of the database and accessing the data table, the method further comprises:
acquiring data to be accessed in a database and identifying the type of the database;
and calling a data type adapter, and converting the data to be accessed in the database into the required data type by using the data type adapter.
3. The multiple data source database access method according to claim 2, wherein said step of calling a data type adapter and converting the data to be accessed by the database into the required data type by using the data type adapter specifically includes:
and converting the data to be accessed of the database between any two types of data including Oracle, Wanli open source, DB2, Mysql, Dameng, HBase, Hive or big gold vault by using the data type adapter.
4. The multiple data source database access method according to claim 2, wherein the obtaining of the data to be accessed by the database, and constructing the designer and the executor corresponding to the database according to the database, so that the designer and the executor satisfy the access steps of the data increment and the data table of the database, specifically includes:
constructing a designer used for connecting the interactive equipment so as to enable the designer to receive configuration access information and processing information transmitted by the interactive equipment;
an executor is configured to connect a processor and a memory such that the executor invokes the processor and the memory to perform data access.
5. The multiple data source database access method according to claim 4, wherein the step of configuring access information and processing information according to the data to be accessed by using a designer corresponding to the database specifically includes:
configuring data input, data processing and data output modes in the database access process by using a visual configuration interface provided by interactive equipment and through the user-defined dragging of a visual configuration node;
and configuring the corresponding relation between the source data source, the target data source and the source data and the target data by filling in the application form by using an application form entry interface provided by the interactive equipment.
6. The multiple data source database access method according to claim 5, wherein the performing, data reading, data processing, and data writing steps on the data to be accessed in the database according to the configuration access information and the processing information by using the corresponding executor of the database specifically include:
reading and processing access data in batches by adopting a rear end actuator of a visual configuration interface, and outputting the processed data;
adopting a default actuator, quickly accessing data to be accessed through a Kafka message queue and distributed deployment, performing read-write separation, and outputting the processed data;
and processing the customized data in the access data according to the preset logic by adopting the personalized extension actuator, and further packaging and writing the data into the Kafka queue for outputting.
7. A multi-data-source database access apparatus, wherein the multi-data-source database access apparatus includes:
the system comprises a construction module, a database access module and a data access module, wherein the construction module is used for acquiring data to be accessed of a database, and constructing a designer and an actuator corresponding to the database according to the database so as to enable the designer and the actuator to meet the data increment of the database and the access of a data table;
the configuration module is used for configuring access information and processing information according to the data to be accessed by utilizing a designer corresponding to the database;
and the execution module is used for reading, processing and writing the data to be accessed in the database according to the configuration access information and the processing information by using the actuator corresponding to the database.
8. Multiple data source database access device, wherein the multiple data source database access device includes: a memory, a processor, and a multiple data source database access program stored on the memory and executable on the processor, the multiple data source database access program when executed by the processor implementing the steps of the multiple data source database access method as recited in any one of claims 1 to 6.
9. Storage medium, on which a multiple data source database access program is stored, which, when executed by a processor, implements the steps of the multiple data source database access method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110368434.7A CN113111111A (en) | 2021-04-06 | 2021-04-06 | Multi-data source database access method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110368434.7A CN113111111A (en) | 2021-04-06 | 2021-04-06 | Multi-data source database access method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113111111A true CN113111111A (en) | 2021-07-13 |
Family
ID=76714035
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110368434.7A Pending CN113111111A (en) | 2021-04-06 | 2021-04-06 | Multi-data source database access method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113111111A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023221520A1 (en) * | 2022-05-20 | 2023-11-23 | 中兴通讯股份有限公司 | Data access method and apparatus, electronic device and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105069142A (en) * | 2015-08-18 | 2015-11-18 | 山大地纬软件股份有限公司 | System and method for extraction, transformation and distribution of data increments |
| CN108846076A (en) * | 2018-06-08 | 2018-11-20 | 山大地纬软件股份有限公司 | The massive multi-source ETL process method and system of supporting interface adaptation |
| CN112286905A (en) * | 2020-10-15 | 2021-01-29 | 北京沃东天骏信息技术有限公司 | Data migration method and device, storage medium and electronic equipment |
-
2021
- 2021-04-06 CN CN202110368434.7A patent/CN113111111A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105069142A (en) * | 2015-08-18 | 2015-11-18 | 山大地纬软件股份有限公司 | System and method for extraction, transformation and distribution of data increments |
| CN108846076A (en) * | 2018-06-08 | 2018-11-20 | 山大地纬软件股份有限公司 | The massive multi-source ETL process method and system of supporting interface adaptation |
| CN112286905A (en) * | 2020-10-15 | 2021-01-29 | 北京沃东天骏信息技术有限公司 | Data migration method and device, storage medium and electronic equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023221520A1 (en) * | 2022-05-20 | 2023-11-23 | 中兴通讯股份有限公司 | Data access method and apparatus, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108958736B (en) | Page generation method and device, electronic equipment and computer readable medium | |
| EP3916501A1 (en) | Digital twin modeling and simulation method, device, and system | |
| CN113111107A (en) | Data comprehensive access system and method | |
| CN106453536A (en) | Network request processing method and system and server | |
| CN110147229A (en) | Flow engine system, method for processing business and device | |
| US20120324421A1 (en) | Application creation tool toolkit | |
| CN113111109A (en) | Interface warehousing analysis access method of data source | |
| CN110633959A (en) | Method, device, equipment and medium for creating approval task based on graph structure | |
| CN109885310A (en) | A kind of method and device reducing mobile phone games Shader module EMS memory occupation | |
| JPH05216739A (en) | Method for controlling structured object for execution with application interface | |
| CN110781180A (en) | Data screening method and data screening device | |
| CN113722055A (en) | Data processing method and device, electronic equipment and computer readable medium | |
| CN111897799A (en) | Hydrological model service system based on process engine | |
| CN113111111A (en) | Multi-data source database access method | |
| CN113111108A (en) | File data source warehousing analysis access method | |
| CN113127000A (en) | Compiling method, device and equipment of application program assembly and storage medium | |
| US9059992B2 (en) | Distributed mobile enterprise application platform | |
| CN115934093A (en) | Applet cross-terminal application method, related device and computer storage medium | |
| CN113568603B (en) | Component object creating and interface method calling method, terminal and storage device | |
| CN115934180A (en) | Workflow engine implementation method, system, device and medium | |
| CN112699111B (en) | Report generation method and device, electronic equipment and computer readable medium | |
| CN114185699A (en) | Data processing method and engine based on discrete parallel model | |
| CN110780859B (en) | Method for realizing service architecture based on user-defined form | |
| CN113111105A (en) | Data customized access method and system based on big data | |
| CN116360752B (en) | Function programming method oriented to java, intelligent terminal and 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 |