CN112445851A - 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 PDF

Info

Publication number
CN112445851A
CN112445851A CN201910823664.0A CN201910823664A CN112445851A CN 112445851 A CN112445851 A CN 112445851A CN 201910823664 A CN201910823664 A CN 201910823664A CN 112445851 A CN112445851 A CN 112445851A
Authority
CN
China
Prior art keywords
data source
distributed data
api
unified
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.)
Pending
Application number
CN201910823664.0A
Other languages
Chinese (zh)
Inventor
冯中强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Shenzhou Taiyue Software Co Ltd
Original Assignee
Beijing Shenzhou Taiyue Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Shenzhou Taiyue Software Co Ltd filed Critical Beijing Shenzhou Taiyue Software Co Ltd
Priority to CN201910823664.0A priority Critical patent/CN112445851A/en
Publication of CN112445851A publication Critical patent/CN112445851A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, 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 implementation method and device, electronic equipment and a storage medium. The method comprises the following steps: a registry is built, and the nodes of the registry are utilized to receive the configuration information of the distributed data source; packaging external interfaces of the distributed data sources into API interfaces with a uniform format; and selectively connecting the distributed data source through the API interface with the uniform format and the configuration information. According to the scheme, the level of unified management, configuration, monitoring and debugging of the operation of the bottom layer of the data source is improved through the construction of the registration center and the unified packaging of each data source interface, the configuration information of the data source can be globally issued only by being modified once, and the workload is greatly reduced; and the problem of uneven level of team members can be solved, and the maintenance and learning cost of the ORM framework is reduced.

Description

Plug-in ORM framework implementation method and device, electronic equipment and storage medium
Technical Field
The invention relates to the technical field of an ORM (object relational mapping) framework, in particular to a plug-in ORM framework implementation method and device, electronic equipment and a storage medium.
Background
The object mapping framework uses metadata to describe the details of the object mapping, the metadata is usually in XML format and is stored in a special object mapping file, and as long as the mapping relationship between the persistent class and the table is provided, the object mapping framework can refer to the information of the mapping file at runtime to persist the object into the database. With the coming of big data era, the data relation is more and more complex, and different requirements are provided for business data, real-time data and cache data. The adoption of the ORM framework is an effective method for realizing the data integration and meeting the data requirements.
However, the conventional ORM integration framework is cumbersome to use, and each project cannot effectively select the most suitable ORM integration framework according to its own characteristics.
Moreover, most distributed databases are deployed on different machines to ensure the efficiency of data batch storage and query, and the connection and call of each database become a current difficulty.
Further, due to the diversification of database APIs of various manufacturers, it is not practical for each project to develop an ORM framework suitable for itself.
Disclosure of Invention
In view of the above problems, the present invention has been made to provide a method, an apparatus, an electronic device, and a storage medium for implementing a pluggable ORM framework, which overcome the above problems or at least partially solve the above problems.
According to an aspect of the present invention, there is provided a method for implementing a pluggable ORM framework, the method including:
a registry is built, and the nodes of the registry are utilized to receive the configuration information of the distributed data source;
packaging external interfaces of the distributed data sources into API interfaces with a uniform format;
and selectively connecting the distributed data source through the API interface with the uniform format and the configuration information.
Optionally, the API interface for encapsulating the external interfaces of the distributed data sources into a uniform format includes:
and forming a name space of each API interface with the uniform format, and configuring data source routing according to the name space and the address of the API interface.
Optionally, the API interface in the unified format at least includes one or more of the following information: unified naming, unified parameters, unified return results, unified external output, unified environment configuration, unified jar dependence and unified logs.
Optionally, the configuring the registry, and receiving the configuration information of the distributed data source by using the node of the registry includes:
and packaging the database API interfaces and the cache library API interfaces in the distributed data sources, and providing the information of the database API interfaces and the cache library API interfaces to the registration center.
Optionally, the method includes: and constructing a Zookeeper service, and determining the Zookeeper service as a registration center.
Optionally, the method includes: and building a Springboot frame, and realizing the API interface with the uniform format by utilizing the component development of the Springboot frame.
Optionally, the method includes: and realizing health check of each distributed data source by using the Endpoint of the Springboot framework.
Another aspect of the present invention provides a plug-in ORM framework implementing apparatus, including:
the system comprises a construction module, a data source module and a data source module, wherein the construction module is suitable for constructing a registration center and receiving configuration information of a distributed data source by using nodes of the registration center;
the packaging module is suitable for packaging the external interfaces of the distributed data sources into API interfaces with a uniform format;
and the connection module is suitable for selectively connecting the distributed data source through the API interface with the uniform format and the configuration information.
In accordance with 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 any one of the above.
According to a further aspect of the invention, there is provided a computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement a method as any one of the above.
In view of the above, the technical solution of the present invention provides a method for implementing a pluggable ORM framework, where the method includes: a registry is built, and the nodes of the registry are utilized to receive the configuration information of the distributed data source; packaging external interfaces of the distributed data sources into API interfaces with a uniform format; and selectively connecting the distributed data source through the API interface with the uniform format and the configuration information. According to the scheme, the level of unified management, configuration, monitoring and debugging of the operation of the bottom layer of the data source is improved through the construction of the registration center and the unified packaging of each data source interface, the configuration information of the data source can be globally issued only by being modified once, and the modification workload is reduced; the problem of uneven levels of team members can be solved, and the maintenance and learning cost of the ORM framework is reduced.
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 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 refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flow chart illustrating a method for implementing a pluggable ORM framework according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a pluggable ORM framework implementation apparatus according to an embodiment of the present invention;
FIG. 3 shows a schematic structural diagram of an electronic device according to one embodiment of the invention;
fig. 4 shows a schematic structural diagram 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 invention are shown in the drawings, it should be understood that the invention can 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 chart illustrating a method for implementing a pluggable ORM framework according to an embodiment of the present invention; the method comprises the following steps:
step S110, a registry is constructed, and the nodes of the registry are used for receiving the configuration information of the distributed data source.
The plug-in type in this embodiment introduces the concept of plug-and-play, and the connection with the database can be realized through the uniform API interface provided by the interface module or the interface component as long as the corresponding interface module or the interface component is introduced into the program. 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 in a node of the registry, so that a communication connection between each distributed data source and the registry is established.
In practical applications, the application program on each machine can use the JavaAPI to obtain the configuration information of each data source in the registry. Each application registers a monitor in a registration center node, once configuration information in the node is changed, each machine acquires the configuration information and uses the latest information to connect a database, so that management is facilitated, only one piece of data is configured in the registration center, and the data does not need to be placed on a plurality of machines; secondly, once the configuration information is changed, an issuing action is performed in the registration center.
Step S120, packaging the external interfaces of the distributed data sources into API interfaces with a uniform format.
The method comprises the steps that a pluggable component is designed and realized between each machine application program and a registration center, the component is composed of API interface submodules with externally unified formats of each data source, and according to different types of each data source, Mysql-API, Hbase-API, Redisl-API, API modules provided by various cache libraries 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 calling parameters, unified returning types, unified externally output results and the like.
And step S130, selectively connecting the distributed data source through the API interface with the uniform format and the configuration information.
Each application program selectively accesses one or more API interfaces with the uniform format according to the requirement of a data request, can be further connected to a registry in a routing addressing mode and the like, and is then connected to a corresponding distributed data source according to configuration information of the registry.
In summary, the method disclosed in this embodiment, first, by constructing the registration center, facilitates management of each distributed data source, reduces workload of configuration information, and only one configuration information needs to be configured to implement global publishing; by setting a uniform API (application program interface), the development workload is reduced, the development efficiency is improved, and conditions are provided for database health check and diagnosis; the problem of uneven levels of team members can be solved, and the maintenance and learning cost of the ORM framework is reduced.
In one embodiment, the API interface for encapsulating the external interface of each of the distributed data sources into a uniform format includes: and forming a name space of each API interface with the uniform format, and configuring data source routing according to the name 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 all distributed data sources are named to form a naming space, then the mapping relation between each named interface and an IP address is established, and finally the accurate connection relation between an application program and the data sources 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 return results, unified external output, unified environment configuration, unified jar dependence and unified logs.
The unified naming comprises the naming of the classes and the naming of the method, so that unified management is realized, and reading and maintenance are convenient. The specific nomenclature includes: class name (Mysql), method name, query (select), add (insert), delete (delete), modify (update), etc. The unified parameters include conditional queries, encapsulation rules, batch insertion update parameter definition as List, and the like. And the results are returned uniformly, all the query return lists, all the additions, deletions, updates, return boolean and the like can be uniformly defined. The unified external output can be packaged as ResultMessage, etc. The unified environment configuration, each product group has its own configuration file, and it is very necessary to unify them, so as to realize the integration of multiple products. And for distributed development, each product group has respective dependence, and integration of a plurality of products is realized through the uniform dependence. The log is unified, the format requirements of the product on the storage and the storage of the log are very high, the log format can be uniformly defined and stored into, for example, an ElasticSearch distributed full-text retrieval framework.
In one embodiment, the distributed data source includes a database and a cache, and the building of the registry includes the following steps of receiving configuration information of the distributed data source by using nodes of the registry: and packaging the database and cache API interfaces in each distributed data source, and providing the information of each database and cache API interface to the registration center.
In order to further realize the unification of the database interfaces, the APIs of the databases are packaged, and the packaged API information is used as configuration information to be registered on corresponding nodes of the registration center, so that the subsequent connection calling is facilitated.
In one embodiment, the method comprises: and constructing a Zookeeper service, and determining the Zookeeper service as a registration center.
Zookeeper is a distributed, open source distributed application program coordination service, and provides software of a consistency service for distributed applications, wherein the provided functions comprise: 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 in different machines, and the registration and connection efficiency is improved.
In one embodiment, the method comprises: and building a Springboot frame, and realizing the API interface with the uniform format by utilizing the component development of the Springboot frame.
The Springboot is selected to realize component-type development, so that the mutual contact among API interface components is reduced, the independent development of 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: and utilizing the Endpoint of the Springboot framework to realize the health check of each distributed data source.
The Spring-boot-activator of the Spring boot framework can help to monitor and manage the Spring boot application, such as health check, audit, statistics, HTTP tracking and the like, and in implementation, a unified interface and a template class can be defined to establish monitoring connection with each data source, and the health check mainly comprises detecting whether the port state of the data source is normal.
FIG. 2 is a schematic diagram of a pluggable ORM framework implementation apparatus according to an embodiment of the present invention; wherein the pluggable ORM framework implementation apparatus 200 includes:
the building module 210 is adapted to build a registry, and receive configuration information of distributed data sources using nodes of the registry.
The plug-in type in this embodiment introduces the concept of plug-and-play, and the connection with the database can be realized through the uniform API interface provided by the interface module or the interface component as long as the corresponding interface module or the interface component is introduced into the program. In the apparatus disclosed in this embodiment, the building module is adapted to build a registry of the distributed data sources, and store configuration information of the distributed data sources on nodes of the registry, so as to establish communication connection between the distributed data sources and the registry.
In practical applications, the application program on each machine can use the JavaAPI to obtain the configuration information of each data source in the registry. Each application registers a monitor in a registration center node, once configuration information in the node is changed, each machine acquires the configuration information and uses the latest information to connect a database, so that management is facilitated, only one piece of configuration information needs to be configured in the registration center, and the configuration information does not need to be put on a plurality of machines; secondly, once the configuration information is changed, an issuing action is performed in the registration center.
And the packaging module 220 is adapted to package the external interfaces of the distributed data sources into API interfaces with a uniform format.
A plug-in type assembly is designed and realized between each machine application program and a registration center, the assembly consists of API interface sub-modules with a uniform format for the outside of each data source, and according to different types of each data source, the assembly can comprise Mysql-API, Hbase-API, Redisl-API, API modules provided by various cache libraries and the like, so that a uniform API interface is provided for the application program to be connected with each distributed data source, wherein the uniform format of the interface can comprise uniform calling parameters, uniform returning types, uniform output results for the outside and the like.
A connection module 230 adapted to selectively connect the distributed data sources through the API interface of the unified format and the configuration information.
Each application program selectively accesses one or more API interfaces with the uniform format according to the requirement of a data request, can be further connected to a registry in a routing addressing mode and the like, and is then connected to a corresponding distributed data source according to configuration information of the registry.
In other embodiments, the pluggable ORM framework implementation apparatus disclosed above is further limited, and corresponds to the above method, for example, the pluggable ORM framework implementation apparatus further includes a routing configuration module and a health check module, which are not described herein again.
In summary, according to the technical scheme disclosed by the invention, the level of unified management, configuration, monitoring and debugging of the bottom layer operation of the data source is improved through the construction of the registration center and the unified packaging of each data source interface, the configuration information of the data source can be globally issued only by being modified once, and the modification workload is reduced; the problem of uneven levels of team members can be solved, and the maintenance cost of an ORM framework and the learning cost of the team members are 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 be used with the teachings herein. The required structure for constructing such a device will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, 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 foregoing 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 invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed 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 device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. 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. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements 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 included in other embodiments, rather than other features, 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 may be used in any combination.
The 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 functionality of some or all of the components in a plug-in ORM framework implementation according to embodiments of the invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
For example, fig. 3 shows a schematic structural diagram of an electronic device according to an embodiment of the 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 storage space 330 storing computer readable program code 331 for performing any of the method steps described above. For example, the storage space 330 for storing the computer readable program code may comprise respective computer readable program codes 331 for respectively implementing various steps in the above method. The computer readable program code 331 may 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 such as described in fig. 4. Fig. 4 shows a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention. The computer readable storage medium 400 has stored thereon a computer readable program code 331 for performing the steps of the method according to the invention, readable by a 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 on 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 usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.

Claims (10)

1. A plug-in ORM framework implementation method is characterized by comprising the following steps:
a registry is built, and the nodes of the registry are utilized to receive the configuration information of the distributed data source;
packaging external interfaces of the distributed data sources into API interfaces with a uniform format;
and selectively connecting the distributed data source through the API interface with the uniform format and the configuration information.
2. The method of claim 1, wherein encapsulating the external interface of each of the distributed data sources into a uniform format API interface comprises:
and forming a name space of each API interface with the uniform format, and configuring data source routing according to the name space and the address of the API interface.
3. The method of claim 1, wherein the uniformly formatted API interface includes at least one or more of the following: unified naming, unified parameters, unified return results, unified external output, unified environment configuration, unified jar dependence and unified logs.
4. The method of claim 1, wherein the distributed data sources comprise a database and a cache, and wherein constructing a registry, and wherein receiving configuration information for distributed data sources using nodes of the registry comprises:
and packaging the database API interfaces and the cache library API interfaces in the distributed data sources, and providing the information of the database API interfaces and the cache library API interfaces to the registration center.
5. The method of any one of claims 1-4, wherein the method comprises:
and constructing a Zookeeper service, and determining the Zookeeper service as a registration center.
6. The method of any one of claims 1-4, wherein the method comprises:
and building a Springboot frame, and realizing the API interface with the uniform format by utilizing the component development of the Springboot frame.
7. The method of claim 6, wherein the method comprises:
and realizing health check of each distributed data source by using the Endpoint of the Springboot framework.
8. A plug-in ORM framework implementation apparatus, the apparatus comprising:
the system comprises a construction module, a data source module and a data source module, wherein the construction module is suitable for constructing a registration center and receiving configuration information of a distributed data source by using nodes of the registration center;
the packaging module is suitable for packaging the external interfaces of the distributed data sources into API interfaces with a uniform format;
and the connection module is suitable for selectively connecting the distributed data source through the API interface with the uniform format and the configuration information.
9. An electronic device, wherein the electronic device comprises: a processor; and a memory arranged to store computer-executable instructions that, when executed, cause the processor to perform the method of any one of claims 1-7.
10. A computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement the method of any of claims 1-7.
CN201910823664.0A 2019-09-02 2019-09-02 Plug-in ORM framework implementation method and device, electronic equipment and storage medium Pending CN112445851A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910823664.0A CN112445851A (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 CN112445851A (en) 2019-09-02 2019-09-02 Plug-in ORM framework implementation method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN112445851A true CN112445851A (en) 2021-03-05

Family

ID=74733874

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910823664.0A Pending CN112445851A (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) CN112445851A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113467855A (en) * 2021-06-24 2021-10-01 北京达佳互联信息技术有限公司 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 (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103294807A (en) * 2013-05-31 2013-09-11 重庆大学 Distributed data management method on basis of multi-level relations
KR20140121749A (en) * 2013-04-08 2014-10-16 주식회사 오비고 Method, server and computer-readable recording media for managing meta store
CN106777375A (en) * 2017-02-07 2017-05-31 山东浪潮云服务信息科技有限公司 A kind of data adaptation system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140121749A (en) * 2013-04-08 2014-10-16 주식회사 오비고 Method, server and computer-readable recording media for managing meta store
CN103294807A (en) * 2013-05-31 2013-09-11 重庆大学 Distributed data management method on basis of multi-level relations
CN106777375A (en) * 2017-02-07 2017-05-31 山东浪潮云服务信息科技有限公司 A kind of data adaptation system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERIKXU: "zookeeper-connection-management", pages 4 - 9, Retrieved from the Internet <URL:https://github.com/ErikXu/zookeeper-connection-management/blob/master/Zookeeper.Mysql/Zookeeper.Mysql/Controllers/TablesController.cs> *
编程玩家: "[奇思异想]使用Zookeeper管理数据库连接串", pages 2 - 9, Retrieved from the Internet <URL:https://www.cnblogs.com/Erik_Xu/p/10631618.html> *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113467855A (en) * 2021-06-24 2021-10-01 北京达佳互联信息技术有限公司 Webpage request processing method and device, electronic equipment and storage medium
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

Similar Documents

Publication Publication Date Title
US10296303B2 (en) Visual programming system
US8418142B2 (en) Architecture for data validation
US7810102B2 (en) Service adaptation of the enterprise services framework
US10120886B2 (en) Database integration of originally decoupled components
CN111142971B (en) Cloud platform application ready checking method suitable for traditional application clouding
CN115934855B (en) Full-link field-level blood margin analysis method, system, equipment and storage medium
US10831565B2 (en) Fault tolerant adapter system to consume database as a service
CN105373536B (en) A kind of method and device for realizing DAO interface
CN112445851A (en) Plug-in ORM framework implementation method and device, electronic equipment and storage medium
CN111913764A (en) Service dependency analysis method, electronic device, and storage medium
CN112698819A (en) Method, device and storage medium for designing tree-oriented object programming program
CN116107669B (en) Operator registration method, device and equipment of deep learning framework and storage medium
US11194616B2 (en) Method, apparatus and system for simultaneously transmitting or receiving multiple managed objects
CN109117152B (en) Service generation system and method
CN116186022A (en) Form processing method, form processing device, distributed form system and computer storage medium
US20190207801A1 (en) System and Method for Rule-Based Simple Network Management Protocol Agent
CN103677846A (en) SQLite database development kit and development method thereof
CN114358936A (en) Intelligent contract operation method based on micro-service block chain
CN113791766A (en) Method for combining data interfaces, electronic device and readable storage medium
US8910183B2 (en) Access to context information in a heterogeneous application environment
CN112965905A (en) Data testing method, device, equipment and storage medium
CN111125232A (en) Method and device for accessing public cloud asset information
CN117667080B (en) Method, device, equipment and medium for determining SCA component dependency information
CN110191141B (en) Service calling information processing method and device and computer system
CN114238459A (en) Heterogeneous data source integrated management method, device and 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