CN112445851B - Plug-in ORM framework implementation method and device, electronic equipment and storage medium - Google Patents
Plug-in ORM framework implementation method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112445851B CN112445851B CN201910823664.0A CN201910823664A CN112445851B CN 112445851 B CN112445851 B CN 112445851B CN 201910823664 A CN201910823664 A CN 201910823664A CN 112445851 B CN112445851 B CN 112445851B
- Authority
- CN
- China
- Prior art keywords
- registry
- distributed data
- unified
- api
- configuration information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000004806 packaging method and process Methods 0.000 claims abstract description 12
- 238000010276 construction Methods 0.000 claims abstract description 11
- 238000011161 development Methods 0.000 claims description 10
- 230000036541 health Effects 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 abstract description 6
- 238000005538 encapsulation Methods 0.000 abstract description 4
- 238000012544 monitoring process Methods 0.000 abstract description 4
- 239000008186 active pharmaceutical agent Substances 0.000 description 49
- 238000010586 diagram Methods 0.000 description 6
- 238000013507 mapping Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 230000010354 integration Effects 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 239000012190 activator Substances 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
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
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a plug-in ORM framework realization method, a device, electronic equipment and a storage medium. The method comprises the following steps: constructing a registry, and receiving configuration information of a distributed data source by using nodes of the registry; packaging the external interfaces of the distributed data sources into API interfaces with uniform formats; and selectively connecting the distributed data sources through the API interface with the uniform format and the configuration information. According to the scheme, the unified management, configuration, monitoring and debugging levels of the bottom operation of the data sources are improved through the construction of the registry and unified encapsulation of all data source interfaces, the global release of the data source configuration information can be realized only by modifying once, and the workload is greatly reduced; and the problem of uneven levels of team members can be solved, and the ORM framework maintenance and learning cost is reduced.
Description
Technical Field
The invention relates to the technical field of ORM frames, in particular to a plug-in ORM frame realization method, a device, electronic equipment and a storage medium.
Background
The ORM (Object Relational Mapping) framework uses metadata to describe the mapping details of the object_relationship, the metadata is generally in an XML format and is stored in a special object_mapping file, and the ORM framework can refer to the information of the mapping file and persist the object into a database when running as long as the mapping relationship between the persisted class and the table is provided. With the advent of the big data age, the data relationship is more and more complex, and different requirements are put forward for business data, real-time data and cache data. The use of the ORM framework is an effective way to achieve the above data integration to meet data requirements.
However, for the conventional ORM integration frame, the use is heavy, and each item cannot effectively select the most suitable ORM integration frame according to the characteristics of the item.
Moreover, distributed databases are mostly deployed on different machines, so as to ensure the efficiency of data batch storage and query, and the connection and call of each database becomes a current difficulty.
Further, due to the diversity of database APIs of various vendors, it is not practical for each project to develop an ORM framework that fits itself.
Disclosure of Invention
The present invention has been made in view of the above problems, and it is an object of the present invention to provide a pluggable ORM framework implementation method, apparatus, electronic device and storage medium that overcomes or at least partially solves the above problems.
According to one aspect of the present invention, there is provided a method for implementing a pluggable ORM framework, the method comprising:
constructing a registry, and receiving configuration information of a distributed data source by using nodes of the registry;
packaging the external interfaces of the distributed data sources into API interfaces with uniform formats;
and selectively connecting the distributed data sources through the API interface with the uniform format and the configuration information.
Optionally, the packaging the external interfaces of the distributed data sources into an API interface in a unified format includes:
and forming a naming space of each API interface in the unified format, and configuring data source routing according to the naming space and the address of the API interface.
Optionally, the API interface in the unified format includes at least one or several of the following information: unified naming, unified parameters, unified returned results, unified external output, unified environment configuration, unified jar dependence, unified log.
Optionally, the distributed data source includes a database and a cache, and the constructing a registry, and receiving, by a node of the registry, configuration information of the distributed data source includes:
and encapsulating database API interfaces and cache API interfaces in the distributed data sources, and providing information of the database API interfaces and the cache API interfaces to the registry.
Optionally, the method includes: building a Zookeeper service, and determining the Zookeeper service as a registry.
Optionally, the method includes: and constructing Springboot a framework, and utilizing the modular development of the Springboot framework to realize the API interfaces of the uniform formats.
Optionally, the method includes: health checking of each of the distributed data sources is accomplished using the Endpoint of the Springboot framework.
Another aspect of the present invention provides a pluggable ORM framework implementation apparatus, the apparatus comprising:
The construction module is suitable for constructing a registry and receiving configuration information of the distributed data sources by utilizing nodes of the registry;
The packaging module is suitable for packaging the external interfaces of the distributed data sources into an API interface with a uniform format;
And the connection module is suitable for selectively connecting the distributed data sources through the API interface with the uniform format and the configuration information.
According to still another aspect of the present invention, there is provided an electronic apparatus including: a processor; and a memory arranged to store computer executable instructions that, when executed, cause the processor to perform a method as described in any of the above.
According to a further aspect of the present invention there is provided a computer readable storage medium storing one or more programs which when executed by a processor implement a method as described in any of the above.
From the above, the technical solution of the present invention provides a method for implementing a pluggable ORM framework, where the method includes: constructing a registry, and receiving configuration information of a distributed data source by using nodes of the registry; packaging the external interfaces of the distributed data sources into API interfaces with uniform formats; and selectively connecting the distributed data sources through the API interface with the uniform format and the configuration information. According to the scheme, the unified management, configuration, monitoring and debugging levels of the bottom operation of the data sources are improved through the construction of the registry and unified encapsulation of all data source interfaces, the global release of the data source configuration information can be realized only by modifying once, and the modification workload is reduced; the problem of uneven levels of team members can be solved, and the maintenance and learning costs of the ORM framework are reduced.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other 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 designate like parts throughout the figures. In the drawings:
FIG. 1 is a flow diagram of a method for implementing a pluggable ORM framework according to one embodiment of the invention;
FIG. 2 illustrates a schematic diagram of a plug-in ORM framework implementation apparatus, according to one embodiment of the invention;
FIG. 3 shows a schematic diagram of an electronic device according to one embodiment of the invention;
Fig. 4 illustrates a schematic structure of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention 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 invention to those skilled in the art.
FIG. 1 is a flow diagram of a method for implementing a pluggable ORM framework according to one embodiment of the invention; the method comprises the following steps:
step S110, a registry is constructed, and the configuration information of the distributed data sources is received by using nodes of the registry.
The plug-and-play concept is introduced in the embodiment, and the connection with the database can be realized by only introducing the corresponding interface module or the interface component into the program and providing the unified API interface through the interface module or the component. In the method disclosed in this embodiment, a registry of each distributed data source is first constructed, and configuration information of each distributed data source is stored on a node of the registry, so that communication connection between each distributed data source and the registry is established.
In practical applications, the java api may be used by an application on each machine to obtain configuration information of each data source in the registry. Each application registers a monitor in a registration center node, and once configuration information in the node is changed, each machine acquires the configuration information and uses the latest information to connect with a database; and secondly, once the configuration information is changed, a published action is performed in the registry.
Step S120, packaging the external interfaces of the distributed data sources into API interfaces with a uniform format.
The method comprises the steps of designing and realizing a plug-in type assembly between each machine application program and a registry, wherein the assembly consists of an API interface submodule with a unified format externally of each data source, and according to different types of each data source, mysql-API, hbase-API, redis-API, API modules provided by various cache libraries and the like can be provided, so that a unified API interface is provided for connecting each distributed data source by the application program, wherein the unified format of the interface can comprise unified calling parameters, unified return types, unified externally output results and the like.
Step S130, selectively connecting the distributed data sources through the API interface in the unified format and the configuration information.
Each application program selectively accesses one or more API interfaces in the unified format according to the requirement of the data request, and then can be connected to the registry by means of routing addressing and the like, and then is connected to the corresponding distributed data source according to the configuration information of the registry.
In summary, according to the method disclosed by the embodiment, firstly, a registry is constructed, so that management of distributed data sources is facilitated, workload of configuration information is reduced, and global release can be realized only by configuring one piece of configuration information; by setting a unified API interface, development workload is reduced, development efficiency is improved, and conditions are provided for database health examination and diagnosis; the problem of uneven levels of team members can be solved, and the maintenance and learning costs of the ORM framework are reduced.
In one embodiment, the packaging the external interfaces of the distributed data sources into the API interface in a unified format includes: and forming a naming space of each API interface in the unified format, and configuring data source routing according to the naming space and the API interface address.
In this embodiment, the correct connection of addressing to the database is achieved by configuring the data source routing. In order to realize unified management, the API interfaces of each distributed data source are named to form a naming space, then the mapping relation between each named interface and the IP address is established, and finally the accurate connection relation between the application program and the data source is established in a routing mode.
In one embodiment, the API interface in the unified format includes at least one or more of the following information: unified naming, unified parameters, unified returned results, unified external output, unified environment configuration, unified jar dependence, unified log.
The unified naming includes naming of classes and naming of methods, unified management is achieved, and reading and maintenance are convenient. Specific naming includes: class name (Mysql), method name, query (select), add (insert), delete (delete), modify (update), etc. The unified parameters include conditional queries, rules that can be encapsulated, batch inserted update parameters defined as List, etc. And the unified return results can define all query return lists in a unified way, and all new additions, deletions, update returns to the boost and the like. Unified external output, can be packaged as ResultMessage, etc. The environment configuration is unified, each product group has a respective configuration file, and the configuration files are very necessary to be unified, so that the integration of a plurality of products is realized. And unified jar dependence, wherein each product group has respective dependence on distributed development, and integration of a plurality of products is realized through unified dependence. The unified log has very high requirement on the storage of the log and the format of the storage, and the log format can be uniformly defined and stored in the distributed full text search framework, for example.
In one embodiment, the distributed data sources include a database and a cache, constructing a registry, and receiving configuration information of the distributed data sources using nodes of the registry includes: and encapsulating database and cache API interfaces in each distributed data source, and providing information of each database and cache API interface to the registry.
In order to further realize unification of database interfaces, APIs of all databases are packaged, and the packaged API information is registered on corresponding nodes of a registry as configuration information, so that subsequent connection calling is facilitated.
In one embodiment, the method comprises: building a Zookeeper service, and determining the Zookeeper service as a registry.
The Zookeeper is a distributed, open source, distributed application coordination service, and provides software for providing consistency services for distributed applications, the provided functions include: configuration maintenance, domain name service, distributed synchronization, group service, etc. The data source configuration information is registered in the Zookeeper, so that the configuration information is prevented from being respectively registered on different machines, and the registration and connection efficiency is improved.
In one embodiment, the method comprises: and constructing Springboot a framework, and utilizing the modular development of the Springboot framework to realize the API interfaces of the uniform formats.
The selection Springboot realizes the component type development, so that the mutual connection among the API interface components is reduced, the independent development of the API interface modules can be realized, the development efficiency is improved, and the development of other components can be realized by utilizing the framework.
In one embodiment, the method comprises: health checking of each of the distributed data sources is accomplished using Endpoint of Springboot framework.
The Spring-boot-activator of Springboot framework can help monitor and manage Springboot applications, such as health check, audit, statistics, HTTP tracking, and the like, can define unified interfaces and templates to establish monitoring connection with each data source in terms of implementation, and the health check mainly comprises detecting whether the port state of the data source is normal.
FIG. 2 illustrates a schematic diagram of a plug-in ORM framework implementation apparatus, according to one embodiment of the invention; wherein the pluggable ORM framework implementation apparatus 200 includes:
The construction module 210 is adapted to construct a registry, and to receive configuration information of the distributed data sources using nodes of the registry.
The plug-and-play concept is introduced in the embodiment, and the connection with the database can be realized by only introducing the corresponding interface module or the interface component into the program and providing the unified API interface through the interface module or the component. In the apparatus disclosed in this embodiment, the construction module is adapted to construct a registry of distributed data sources, and store configuration information of the distributed data sources on nodes of the registry, thereby establishing communication connection between the distributed data sources and the registry.
In practical applications, the java api may be used by an application on each machine to obtain configuration information of each data source in the registry. Each application registers a monitor in a registration center node, and once configuration information in the node is changed, each machine acquires the configuration information and uses the latest information to connect with a database; and secondly, once the configuration information is changed, a published action is performed in the registry.
The encapsulation module 220 is adapted to encapsulate the external interfaces of the distributed data sources into API interfaces with a uniform format.
The plug-in type assembly is designed between each machine application program and the registration center, and consists of an API interface submodule with a unified format for each data source, and according to different types of each data source, mysql-API, hbase-API, redis-API, various API modules provided by a cache library and the like can be provided, so that a unified API interface is provided for the application program to connect each distributed data source, wherein the unified format of the interface can comprise unified call parameters, unified return types, unified external output results and the like.
A connection module 230 adapted to selectively connect the distributed data sources via the API interface of the unified format and the configuration information.
Each application program selectively accesses one or more API interfaces in the unified format according to the requirement of the data request, and then can be connected to the registry by means of routing addressing and the like, and then is connected to the corresponding distributed data source according to the configuration information of the registry.
In other embodiments, the above-disclosed pluggable ORM framework implementation apparatus is further limited, and corresponds to the above-described method, for example, the pluggable ORM framework implementation apparatus further includes a routing configuration module, a health check module, and the like, which are not described herein.
In summary, according to the technical scheme disclosed by the invention, the level of unified management, configuration, monitoring and debugging of the bottom operation of the data source is improved through the construction of the registry and unified encapsulation of all data source interfaces, the global release of the data source configuration information can be realized only by modifying once, and the modification workload is reduced; the problem of uneven levels of team members can be solved, and the cost of ORM framework maintenance and team member learning is reduced.
It should be noted that:
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose devices may also be used with the teachings herein. The required structure for the construction of such devices is apparent from the description above. In addition, the present invention is not directed to any particular programming language. It will be appreciated that the teachings of the present invention described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.
Various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a pluggable ORM framework implementation apparatus according to embodiments of the present invention. The present invention can also be implemented as an apparatus or device program (e.g., a computer program and a computer program product) for performing a portion or all of the methods described herein. Such a program embodying the present invention may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
For example, fig. 3 shows a schematic structural diagram of an electronic device according to an embodiment of the present invention. The electronic device 300 comprises a processor 310 and a memory 320 arranged to store computer executable instructions (computer readable program code). The memory 320 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. The memory 320 has a memory space 330 storing computer readable program code 331 for performing any of the method steps described above. For example, the memory space 330 for storing computer readable program code may include respective computer readable program code 331 for implementing the respective steps in the above method, respectively. The computer readable program code 331 can be read from or written to one or more computer program products. These computer program products comprise a program code carrier such as a hard disk, a Compact Disc (CD), a memory card or a floppy disk. Such a computer program product is typically a computer readable storage medium as described for example in fig. 4. Fig. 4 illustrates a schematic structure of a computer-readable storage medium according to an embodiment of the present invention. The computer readable storage medium 400 stores computer readable program code 331 for performing the steps of the method according to the invention, which may be read by the processor 310 of the electronic device 300, which computer readable program code 331, when executed by the electronic device 300, causes the electronic device 300 to perform the steps of the method described above, in particular the computer readable program code 331 stored by the computer readable storage medium may perform the method shown in any of the embodiments described above. The computer readable program code 331 may be compressed in a suitable form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
Claims (8)
1. A method for implementing a pluggable ORM framework, the method comprising:
Constructing a registry, and receiving configuration information of distributed data sources by using nodes of the registry, wherein each machine application program obtains the configuration information of each distributed data source in the registry through a Java API, and each application program registers a monitor at the nodes of the registry so that each machine obtains the latest configuration information to connect the distributed data sources;
the distributed data source comprises a database and a buffer library, the construction of the registry, and the receiving of the configuration information of the distributed data source by the nodes of the registry comprises:
Encapsulating a database API interface and a cache API interface in each distributed data source, and providing information of each database API interface and each cache API interface to the registry;
Packaging external interfaces of the distributed data sources into API interfaces with uniform formats, forming namespaces of the API interfaces with the uniform formats, configuring data source routes according to the namespaces and addresses of the API interfaces, and disposing the API interfaces with the uniform formats between machine application programs and a registry in the form of pluggable components;
And selectively connecting the distributed data sources through the API interfaces in the unified format and the configuration information, wherein each machine application program selectively accesses one or more API interfaces in the unified format, is connected to a registry in a routing addressing mode, and is then connected to the corresponding distributed data sources according to the configuration information of the registry.
2. The method of claim 1, wherein the unified format API interface includes at least one or more of the following information: unified naming, unified parameters, unified returned results, unified external output, unified environment configuration, unified jar dependence, unified log.
3. The method according to any one of claims 1-2, wherein the method comprises:
building a Zookeeper service, and determining the Zookeeper service as a registry.
4. The method according to any one of claims 1-2, wherein the method comprises:
And constructing Springboot a framework, and utilizing the modular development of the Springboot framework to realize the API interfaces of the uniform formats.
5. The method of claim 4, wherein the method comprises:
Health checking of each of the distributed data sources is accomplished using the Endpoint of the Springboot framework.
6. A pluggable ORM framework implementation apparatus, the apparatus comprising:
The system comprises a construction module, a configuration module and a configuration module, wherein the construction module is suitable for constructing a registry, and utilizes nodes of the registry to receive configuration information of distributed data sources, wherein each machine application program obtains the configuration information of each distributed data source in the registry through a Java API, and each application program registers a monitor at the nodes of the registry so that each machine obtains the latest configuration information to connect the distributed data sources;
the distributed data source comprises a database and a buffer library, the construction of the registry, and the receiving of the configuration information of the distributed data source by the nodes of the registry comprises:
Encapsulating a database API interface and a cache API interface in each distributed data source, and providing information of each database API interface and each cache API interface to the registry;
The packaging module is suitable for packaging the external interfaces of the distributed data sources into an API interface with a unified format, and the API interface with the unified format is deployed between each machine application program and a registry in the form of a pluggable component;
The packaging module is further adapted to:
Forming a naming space of each API interface in the unified format, and configuring a data source route according to the naming space and the address of the API interface;
And the connection module is suitable for selectively connecting the distributed data sources through the API interfaces in the unified format and the configuration information, wherein each machine application program selectively accesses one or more API interfaces in the unified format, is connected to the registry in a routing addressing mode, and is then connected to the corresponding distributed data sources according to the configuration information of the registry.
7. An electronic device, wherein the electronic device comprises: a processor; and a memory arranged to store computer executable instructions which, when executed, cause the processor to perform the method of any of claims 1-5.
8. A computer readable storage medium storing one or more programs which, when executed by a processor, implement the method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910823664.0A CN112445851B (en) | 2019-09-02 | 2019-09-02 | Plug-in ORM framework implementation method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910823664.0A CN112445851B (en) | 2019-09-02 | 2019-09-02 | Plug-in ORM framework implementation method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112445851A CN112445851A (en) | 2021-03-05 |
| CN112445851B true CN112445851B (en) | 2024-07-16 |
Family
ID=74733874
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910823664.0A Active CN112445851B (en) | 2019-09-02 | 2019-09-02 | Plug-in ORM framework implementation method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112445851B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113467855B (en) * | 2021-06-24 | 2024-03-19 | 北京达佳互联信息技术有限公司 | Webpage request processing method and device, electronic equipment and storage medium |
| CN113742103A (en) * | 2021-08-30 | 2021-12-03 | 北京爱奇艺科技有限公司 | Cross-data-source service implementation method and device and electronic equipment |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106777375A (en) * | 2017-02-07 | 2017-05-31 | 山东浪潮云服务信息科技有限公司 | A kind of data adaptation system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101523266B1 (en) * | 2013-04-08 | 2015-05-28 | 주식회사 오비고 | Method, server and computer-readable recording media for managing meta store |
| CN103294807B (en) * | 2013-05-31 | 2017-03-01 | 重庆大学 | A kind of DDM method based on multi-layer relation |
-
2019
- 2019-09-02 CN CN201910823664.0A patent/CN112445851B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106777375A (en) * | 2017-02-07 | 2017-05-31 | 山东浪潮云服务信息科技有限公司 | A kind of data adaptation system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112445851A (en) | 2021-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9420034B2 (en) | Providing services to multiple tenants of an application | |
| US8046772B2 (en) | System and method for enterprise application interactions | |
| CN110413288A (en) | Using dispositions method, device, server and storage medium | |
| US10120886B2 (en) | Database integration of originally decoupled components | |
| US20090187879A1 (en) | Architecture for data validation | |
| US11106641B2 (en) | Supporting graph database backed object unmarshalling | |
| US10831565B2 (en) | Fault tolerant adapter system to consume database as a service | |
| CN112445851B (en) | Plug-in ORM framework implementation method and device, electronic equipment and storage medium | |
| WO2023142911A1 (en) | Service processing method and device | |
| CN112068850A (en) | Method and device for creating service product instance and electronic equipment | |
| CN113296758A (en) | Front-end component library construction method and device and storage medium | |
| CN111381820A (en) | Method and device for automatically generating API based on GUI | |
| CN113791766A (en) | Method for combining data interfaces, electronic device and readable storage medium | |
| CN114238459A (en) | A method, device and system for integrated management of heterogeneous data sources | |
| CN113779452A (en) | Data processing method, device, equipment and storage medium | |
| CN116700745A (en) | Application deployment method and device based on container cloud platform, electronic equipment and medium | |
| CN116467049A (en) | Method, device, system, equipment and medium for constructing micro-service container mirror image | |
| CN116954572A (en) | AI capability encapsulation method, AI capability encapsulation device, electronic equipment and storage medium | |
| CN116186022A (en) | Form processing method, form processing device, distributed form system and computer storage medium | |
| CN114677114A (en) | Approval process generation method and device based on graph dragging | |
| CN118449995B (en) | Extensible simulation service framework system based on micro-service architecture | |
| US11392433B1 (en) | Generation of asynchronous application programming interface specifications for messaging topics | |
| US20160294928A1 (en) | System and method for supporting javascript activities in a process defined by a process execution language for execution in a soa middleware environment | |
| CN114780540A (en) | Metadata processing method and device for big data platform and electronic equipment | |
| CN110191141B (en) | Service calling information processing method and device and computer system |
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 |