CN111400110B - Database access management system - Google Patents
Database access management system Download PDFInfo
- Publication number
- CN111400110B CN111400110B CN202010164911.3A CN202010164911A CN111400110B CN 111400110 B CN111400110 B CN 111400110B CN 202010164911 A CN202010164911 A CN 202010164911A CN 111400110 B CN111400110 B CN 111400110B
- Authority
- CN
- China
- Prior art keywords
- database
- router
- external service
- library
- service application
- 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
- 238000012544 monitoring process Methods 0.000 claims abstract description 9
- 230000003993 interaction Effects 0.000 claims description 4
- 230000008685 targeting Effects 0.000 claims description 3
- 238000000034 method Methods 0.000 claims 1
- 238000010926 purge Methods 0.000 claims 1
- 238000007726 management method Methods 0.000 description 37
- 238000010586 diagram Methods 0.000 description 8
- 238000013507 mapping Methods 0.000 description 5
- 101001110283 Canis lupus familiaris Ras-related C3 botulinum toxin substrate 1 Proteins 0.000 description 3
- 101001110313 Homo sapiens Ras-related C3 botulinum toxin substrate 2 Proteins 0.000 description 3
- 102100022129 Ras-related C3 botulinum toxin substrate 2 Human genes 0.000 description 3
- 102100022122 Ras-related C3 botulinum toxin substrate 1 Human genes 0.000 description 2
- 108010062302 rac1 GTP Binding Protein Proteins 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention discloses a database access management system. The system comprises: the system comprises a database routing management layer and a database deployed at a cloud end, wherein the database routing management layer comprises a set number of routers, and the set number is the same as the number of the databases deployed at the cloud end; each router manages one database of the cloud end in a one-to-one correspondence manner, each database is recorded as a main database in the corresponding router, each router also manages one standby database in a one-to-one correspondence manner, and the standby database is a database which is deployed in the cloud end and is different from the main database in the router to which the standby database belongs; and the router is used for controlling the managed standby library to respond to the database access request when receiving the database access request of the external service application and monitoring that the managed main library is in a downtime state so as to realize the data writing access from the external service application to the standby library. According to the technical scheme provided by the embodiment of the invention, the realization of external business application is not influenced by database downtime, and the stability of the system is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of database application, in particular to a database access management system.
Background
Oracle RAC (Real Application Clusters, real-time application cluster) is a technology adopted in Oracle new version databases, is a high availability technology, and is also a core technology of Oracle databases supporting network computing environments.
The Oracle RAC provides cluster software and storage management software at the present stage, so that the application cost is reduced for users, when the application scale needs to be expanded, the performance of the system can be ensured only by expanding the system according to the need, and the high availability of the Oracle RAC is set on the basis of hardware, namely on the basis of hardware facilities of a physical machine, and the load of a plurality of nodes is balanced, so that problems can be found in time and faults can be removed when one RAC is down.
When the Oracle RAC is deployed on the cloud virtual machine, high availability of the Oracle RAC becomes unpredictable because hardware facilities of the virtual machine are virtual, and when the RAC is down, external service application for calling the RAC is also affected, so that the availability and stability of the system are reduced.
Disclosure of Invention
The invention provides a database access management system, which is used for realizing high availability of a database and improving the stability of the system.
The embodiment of the invention provides a database access management system, which comprises: a database route management layer and a database deployed at the cloud,
the database route management layer comprises a set number of routers, wherein the set number is the same as the number of databases deployed in the cloud;
each router manages one database of the cloud end in a one-to-one correspondence manner, each database is recorded as a main database in the corresponding router, each router also manages one standby database in a one-to-one correspondence manner, and the standby database is a database which is deployed in the cloud end and is different from the main database in the router to which the standby database belongs;
and the router is used for controlling the managed standby library to respond to the database access request when receiving the database access request of the external service application and monitoring that the managed main library is in a downtime state so as to realize the data writing access from the external service application to the standby library.
Further, the database access management system further includes: the routing configuration layer is provided with a routing layer,
the route configuration layer is respectively connected with the external service application and the database route management layer, and is used for analyzing the database access request sent by the external service application, determining a target router corresponding to the external service application in the database route management layer and forwarding the database access request to the target router.
Further, the routing configuration layer includes:
the information analysis module is used for analyzing a database access request sent by the external service application and acquiring database access object information of the external service application;
the target determining module is used for determining a target router corresponding to the external service application according to the database access object information;
and the request forwarding module is used for forwarding the database access request to the target router.
Further, the target determining module specifically includes:
a first determining unit, configured to determine, when an external service application corresponding to the database access object information shares a data table with the same table name with other external service applications, a target router according to a special routing configuration rule, where the database includes a plurality of data tables;
the second determining unit is used for determining the target router according to the naming space route configuration rule when the external service application corresponding to the database access object information and other external service applications do not share the data table with the same table name and the database access object information contains an effective naming space;
and the third determining unit is used for determining the target router according to the default route configuration rule when the external service application corresponding to the database access object information and other external service applications do not share the data table with the same table name and the database access object information does not contain the effective naming space.
Further, the first determining unit is specifically configured to:
determining a first data table with an identification field according to an external service application corresponding to the database access object information;
and determining a target database in which the first data table is located, and determining a router taking the target database as a main library as a target router.
Further, the second determining unit is specifically configured to:
determining a second data table corresponding to the database access object information according to the effective naming space contained in the database access object information;
and determining a target database where the second data table is located, and determining a router taking the target database as a main library as a target router.
Further, the third determining unit is specifically configured to:
and selecting one cloud deployed database as a target database according to a random principle, and determining a router taking the target database as a main database as a target router.
Further, the database deployed in the cloud is configured to synchronize the service data stored in the corresponding external service application to the database in the router to which the external service application belongs as the master database after finishing interaction with the external service application when the backup database in the router is accessed by the external service application, and clean the service data.
Further, the router is further configured to, after controlling the managed standby library to respond to the database access request, control the main library to respond to the database access request if it is monitored that the main library is currently in a normal working state or is restored to the normal working state by downtime.
The embodiment of the invention provides a database access management system, which comprises: the system comprises a database routing management layer and a database deployed at a cloud end, wherein the database routing management layer comprises a set number of routers, and the set number is the same as the number of the databases deployed at the cloud end; each router manages one database of the cloud end in a one-to-one correspondence manner, each database is recorded as a main database in the corresponding router, each router also manages one standby database in a one-to-one correspondence manner, and the standby database is a database which is deployed in the cloud end and is different from the main database of the router; and the router is used for controlling the managed standby library to respond to the database access request when receiving the database access request of the external service application and monitoring that the managed main library is in a downtime state so as to realize the data writing access from the external service application to the standby library. By adopting the technical scheme, the main library and the standby library which are in one-to-one correspondence with the cloud deployment database are configured in each router, when the main library is in a downtime state, the standby library is controlled to finish responding to the access request of the database and writing access of external service application data, the problem that high availability cannot be predicted when the database is deployed on the cloud virtual machine can be solved, and when one database is downtime, the other database is started in time, so that the realization of external service application is not influenced by the downtime of the database, and the stability of the system is improved.
Drawings
FIG. 1 is a schematic diagram of a database access management system according to a first embodiment of the present invention;
FIG. 2 is a schematic diagram of a database access management system according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a routing configuration layer in a second embodiment of the present invention;
fig. 4 is a diagram showing an example of the structure of a database access management system according to the second embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings. Furthermore, embodiments of the invention and features of the embodiments may be combined with each other without conflict.
Example 1
Fig. 1 is a schematic structural diagram of a database access management system according to a first embodiment of the present invention, where the database access management system includes: a database route management layer 10 and a database 11 deployed in the cloud.
The database route management layer 10 includes a set number of routers 12, where the set number is the same as the number of databases 11 deployed in the cloud.
Each router 12 manages one database 11 of the cloud end in a one-to-one correspondence manner, each database 11 is a main database in the corresponding router 12, each router 12 also manages one standby database in a one-to-one correspondence manner, and the standby database is a database 11 which is deployed in the cloud end and is different from the main database in the router 12 to which the standby database belongs.
The router 12 is configured to, when receiving a database access request of the external service application 13, control a managed standby database to respond to the database access request if it is monitored that the managed main database is in a down state, so as to implement data writing access from the external service application 13 to the standby database.
The database route management layer 10 is understood to be composed of a set number of routers 12, and is used to manage data objects of a plurality of different routers 12.
The router 12 may be understood as a hardware device for connecting two or more networks, and may be understood herein as a hardware device for managing two or more databases 11 deployed in the cloud. The number of the routers 12 is the same as that of the databases 11 deployed in the cloud and one database 11 is managed in a one-to-one correspondence manner to serve as a main database, and meanwhile one database 11 different from the main database is managed in a one-to-one correspondence manner to serve as a standby database, and optionally, the main database in one router 12 is a standby database in another router 12 matched with the main database, and the main database in the other router 12 matched with the main database is a standby database in the router 12.
The database 11 is understood to be a repository for organizing, storing and managing data according to a data structure, which is a set of data stored together in a manner that can be shared with a plurality of users, has as little redundancy as possible, and is independent of the application. Illustratively, in the Oracle database framework, a real-time application cluster (Real Application Clusters, RAC) can be understood as a database.
Specifically, a plurality of databases 11 are deployed in the cloud, and correspondingly, routers 12 with the same number as the cloud databases are deployed in the database route management layer 10. Each router 12 and the database 11 in the cloud form a one-to-one corresponding management relationship, the corresponding managed databases 11 are the main databases in the corresponding routers 12, each router 12 also manages one database 11 in the databases 11 in the cloud except the main databases as a standby database, wherein the two databases 11 are the main database and the standby database in each other in the pair of routers 12, i.e. the main database in one router 12 is the standby database in the other router 12, and the standby database in one router 12 is the main database in the corresponding other router 12. When receiving a database access request from the external service application 13, if the router 12 monitors that the main library managed by the router is in a downtime state, the router controls the standby library managed by the router to respond to the database access request so as to respond to the external service application 13, thereby realizing the data writing access of the external service application 13.
The external service application 13 is understood as an external application program that makes a rewrite call to the database contents via the data access layer (Data Access Object, DAO) input system.
Further, the database 11 deployed in the cloud is configured to synchronize the service data stored in the corresponding external service application 13 to the database 11 in the router 12 as the master database after finishing the interaction with the external service application 13 when the backup database in the router 12 is accessed by the external service application 13, and clean up the service data.
Wherein the service data stored by the external service application 13 can be written into the database in the form of a data table.
Specifically, when the router 12 receives the access of the external service application 13, the main library is in a downtime state, and then the standby library in the router 12 is accessed, and at this time, the data writing access of the external service application 13 to the standby library and the reading access of the data stored in the standby library can be completed, and when the standby library finishes the interaction with the external service application 13, the standby library synchronizes the service data written in the library by the external service application 13 to the database 11 serving as the main library in the router 12 to which the standby library belongs, and clears the service data in the standby library.
Further, the router 12 is further configured to, after controlling the managed standby library to respond to the database access request, control the main library to respond to the database access request if it is monitored that the main library is currently in a normal state or is restored to a normal working state from a down state.
Specifically, the router 12 monitors the working state of the master library through a heartbeat program, and when the master library is in a normal working state, takes the master library as a current use library to respond to the database access request. When the main library is in a downtime state, the standby library is used as a current use library to respond to the database access request, meanwhile, the working state of the main library is monitored continuously, and when the working state of the main library is recovered to be normal, the main library is used as the current use library again to respond to the database access request. Optionally, after the main library resumes the normal working state, the service data stored in the external service application 13 in the downtime stage is synchronized from the standby library to the main library, and the service data stored in the standby library is deleted.
The embodiment of the invention provides a database access management system, which comprises: the system comprises a database routing management layer and a database deployed at a cloud end, wherein the database routing management layer comprises a set number of routers, and the set number is the same as the number of the databases deployed at the cloud end; each router manages one database of the cloud end in a one-to-one correspondence manner, each database is recorded as a main database in the corresponding router, each router also manages one standby database in a one-to-one correspondence manner, and the standby database is a database which is deployed in the cloud end and is different from the main database of the router; and the router is used for controlling the managed standby library to respond to the database access request when receiving the database access request of the external service application and monitoring that the managed main library is in a downtime state so as to realize the data writing access from the external service application to the standby library. By adopting the technical scheme, the main library and the standby library which are in one-to-one correspondence with the cloud deployment database are configured in each router, when the main library is in a downtime state, the standby library is controlled to finish responding to the access request of the database and writing access of external service application data, the problem that high availability cannot be predicted when the database is deployed on the cloud virtual machine can be solved, and when one database is downtime, the other database is started in time, so that the realization of external service application is not influenced by the downtime of the database, and the stability of the system is improved.
Example two
Fig. 2 is a schematic structural diagram of a database access management system according to a second embodiment of the present invention, where the technical solution of the present embodiment is further refined on the basis of the above technical solution, and the database access management system includes: a database route management layer 10 and a database 11 deployed in the cloud.
The database route management layer 10 includes a set number of routers 12, where the set number is the same as the number of databases 11 deployed in the cloud.
Each router 12 manages one database 11 of the cloud end in a one-to-one correspondence manner, each database 11 is a main database in the corresponding router 12, each router 12 also manages one standby database in a one-to-one correspondence manner, and the standby database is a database 11 which is deployed in the cloud end and is different from the main database in the router 12 to which the standby database belongs.
The router 12 is configured to, when receiving a database access request of the external service application 13, control a managed standby database to respond to the database access request if it is monitored that the managed main database is in a down state, so as to implement data writing access from the external service application 13 to the standby database.
The database access management system further comprises a routing configuration layer 14, wherein the routing configuration layer 14 is respectively connected with the external service application 13 and the database route management layer 10, and is used for analyzing a database access request sent by the external service application 13, determining a target router corresponding to the external service application 13 in the database route management layer 10, and forwarding the database access request to the target router.
The routing configuration layer 14 may be understood as a data management layer for determining a target database according to a database access request of the external service application 13 and assigning the router 12 having the target database as a target router to the external service application 13 for an access response.
Specifically, the external service application 13 sends a database access request through the DAO layer, the routing configuration layer 14 receives the database access request to determine the database 11 to be accessed by the external service application 13, determines the router 12 taking the database 11 as a main library as a target router according to the determined database 11, determines the position of the target router in the database routing management layer 10, forwards the database access request to the target router, monitors the working state of the main library therein, and completes the data writing access of the external service application 13 according to the working state of the main library.
Further, fig. 3 is a schematic structural diagram of a routing configuration layer according to a second embodiment of the present invention, where the routing configuration layer 14 specifically includes: an information analysis module 21, a targeting module 22, and a request forwarding module 23.
The information analysis module 21 is configured to analyze the database access request sent by the external service application 13, and obtain the database access object information of the external service application 13. The target determining module 22 is configured to determine a target router corresponding to the external service application 13 according to the database access object information. A request forwarding module 23, configured to forward the database access request to the target router.
Further, the targeting module 22 includes:
a first determining unit, configured to determine, if the external service application 13 corresponding to the database access object information shares a data table with the same table name with other external service applications 13, the target router according to a special routing configuration rule, where the database includes a plurality of data tables;
a second determining unit, configured to determine, if the external service application 13 corresponding to the database access object information and the other external service applications 13 do not share a data table with the same table name, and the database access object information includes an effective namespace, the target router according to a namespace route configuration rule;
and a third determining unit, configured to determine, according to a default route configuration rule, the target router when the external service application 13 corresponding to the database access object information does not share a data table with the same table name with other external service applications 13, and the database access object information does not include an effective namespace.
The external service application 13 and other external service applications 13 that correspond to the database access object information share the data table with the same table name, which can be understood as the data table with the same table name corresponding to the two external service applications 13, where the data tables exist in two different databases 11 and the data stored in the two data tables are different, and the external service applications 13 identify the corresponding data table through the identification field.
The special routing configuration rule can be understood as mapping the router according to a thread local variable (ThreadLocal), and mapping the data table with different identification fields with the same table name, the database to which the data table belongs and the router is completed by setting the ThreadLocal variable through the service layer code.
The name space is understood as a code number, such as a name, used for organizing and utilizing codes, and is used for representing table names of data tables under the iBatis database management framework in the object mapping framework.
The namespace route configuration rule can be understood as a namespace obtained from the database access object information, and the corresponding database and router are determined according to the configured namespace mapping.
The default routing configuration rule may be understood as an unconfigured configuration rule that randomly selects one configuration rule from the database 11 deployed in the cloud to access the router 12 taking the database 11 as a main library.
The priority order of the three routing configuration rules is configured according to the special routing configuration rules, the naming space routing configuration is carried out under the condition of no special routing configuration, and if the three routing configuration rules do not exist, the target router is determined according to the default routing configuration rules.
Further, the first determining unit is specifically configured to:
when the external service application 13 corresponding to the database access object information and other external service applications 13 share the data table with the same table name, determining a first data table with an identification field according to the external service application 13 corresponding to the database access object information; the database 11 where the first data table is located is determined as a target database, and the router 12 having the target database as a master is determined as a target router.
Specifically, when the external service application 13 corresponding to the database access object information is an application sharing the same table name data table as other external service applications 13, the routing configuration layer 14 obtains, from the database access object information, identification fields of the external service application 13 sending the database access object information, which are different from other external service applications 13, determines the first data table and the database 11 containing the first data table according to the identification fields, uses the database 11 as a target database, and finds the router 12 using the target database as a main database in the database routing management layer 10, and determines the target router.
Further, the second determining unit is specifically configured to:
when the external service application 13 corresponding to the database access object information and other external service applications 13 do not share the data table with the same table name and the database access object information contains an effective naming space, determining a second data table corresponding to the database access object information according to the effective naming space contained in the database access object information; the target database in which the second data table is located is determined, and the router 12 having the target database as the master is determined as the target router.
Specifically, when the external service application 13 corresponding to the database access object information and other external service applications 13 do not share the data table with the same table name, acquiring a namespace corresponding to the database access object information under the iBatis framework according to a function, judging whether the namespace corresponding to the database access object information is a valid namespace according to the configured namespace mapping, if so, determining a second data table corresponding to the valid namespace according to the valid namespace, determining a database 11 containing the second data table, taking the database 11 as a target database, and finding a router 12 taking the target database as a main database in the database route management layer 10 to determine the target router.
Further, the third determining unit is specifically configured to:
when the external service application 13 corresponding to the database access object information does not share the data table with the same table name with other external service applications 13 and the database access object information does not contain an effective naming space, selecting one cloud deployed database 11 as target data according to a random principle, and determining the router 12 taking the target database as a main base as a target router.
Fig. 4 is a schematic diagram of a structure example of a database access management system according to a second embodiment of the present invention, specifically, an external service application accesses a DAO layer and sends a database access request to the DAO layer, determines a database access object and database access object information, and sends the database access request to a routing configuration layer, where the routing configuration layer determines a sub-library and sub-table route to which the external service application should access according to a preset routing configuration rule, and each sub-library and sub-table route includes two databases below, which are a main library and a standby library respectively. Taking two databases as an example, RAC1 and RAC2 are taken as a main base and a preferential use base in the database-division and table-division route 1, RAC2 is taken as a standby base, and RAC2 is taken as a main base and RAC1 is taken as a standby base in the database-division and table-division route 2, so the database-division and table-division routes 1 and 2 are a pair of routers for managing a pair of databases which are the main base and the standby base. When one of the sub-library sub-table routes receives the database access request information transmitted by the route configuration layer, the sub-library sub-table route acquires the working state of the main library in the route from the main library monitoring program. The monitoring includes two cases, namely monitoring whether the main library is down when the main library is not down, and monitoring whether the main library is restored when the main library is in the down state. When the working state of the main library is monitored to be normal, the main library is used as a current use library, and a database access request of external service application is responded; when the monitoring main library is down, the standby library is used as a current use library, and a database access request of an external service application is responded, wherein only a data writing request in the database access request and a reading request of existing data in the backup library can be responded. When the working state of the main library is monitored to be recovered to be normal, the data received by the standby library in the downtime stage of the main library can be automatically or manually synchronized to the main library, and the data in the standby library can be deleted. Further, if the main library and the standby library are in the downtime state, the external service application fails to access, returns error information and reminds the background to perform manual processing.
According to the technical scheme of the embodiment, the corresponding accessed data table is determined according to the database access request sent by the external service application, the corresponding target database and the target router determined by the script target database are determined according to the data table, the databases in different routers are the main database and the backup database, the problems that when the main database in the router is not down, the utilization rate of the database serving as the backup database is low and resources are wasted are solved, the utilization rate of the database is improved, meanwhile, when the main database is down, the database is timely switched to the backup database, the response of the external service application is ensured, and the stability and the usability of the system are improved.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (9)
1. A database access management system, comprising: a database route management layer and a database deployed at the cloud,
the database route management layer comprises a set number of routers, wherein the set number is the same as the number of databases deployed in the cloud;
each router is used for managing one database of the cloud end in a one-to-one correspondence manner, each database is recorded as a main database in a corresponding router, each router is used for managing one standby database in a one-to-one correspondence manner, and each standby database is a database which is deployed in the cloud end and is different from the main database in the router to which the standby database belongs;
the router is used for controlling the managed standby library to respond to the database access request when receiving the database access request of the external service application and monitoring that the managed main library is in a downtime state so as to realize the data writing access from the external service application to the standby library;
the method comprises the steps of routing a pair of routers in a management layer aiming at the database, wherein a main library in one router is a standby library in the other router, and the standby library in one router is the main library in the other router;
the router monitors the working state of the main library through a main library monitoring program, and when the main library is in a downtime state, the router controls the standby library to respond to a data writing request in the database access request and a reading request of the existing data in the standby library.
2. The system of claim 1, further comprising: the routing configuration layer is provided with a routing layer,
the routing configuration layer is respectively connected with the external service application and the database routing management layer, and is used for analyzing a database access request sent by the external service application, determining a target router corresponding to the external service application on the database routing management layer, and forwarding the database access request to the target router.
3. The system of claim 2, the routing configuration layer comprising:
the information analysis module is used for analyzing the database access request sent by the external service application and acquiring the database access object information of the external service application;
the target determining module is used for determining a target router corresponding to the external service application according to the database access object information;
and the request forwarding module is used for forwarding the database access request to the target router.
4. A system according to claim 3, the targeting module comprising in particular:
a first determining unit, configured to determine, when the external service application corresponding to the database access object information shares a data table with the same table name with other external service applications, the target router according to a special routing configuration rule, where the database includes a plurality of data tables;
a second determining unit, configured to determine, when the external service application corresponding to the database access object information and other external service applications do not share a data table with the same table name, and the database access object information includes an effective namespace, the target router according to a namespace route configuration rule;
and the third determining unit is used for determining the target router according to a default route configuration rule when the external service application corresponding to the database access object information and other external service applications do not share the data table with the same table name and the database access object information does not contain an effective naming space.
5. The system according to claim 4, wherein the first determining unit is specifically configured to:
determining a first data table with an identification field according to the external service application corresponding to the database access object information;
and determining a target database where the first data table is located, and determining a router taking the target database as a main library as the target router.
6. The system according to claim 4, wherein the second determining unit is specifically configured to:
determining a second data table corresponding to the database access object information according to the effective naming space contained in the database access object information;
and determining a target database where the second data table is located, and determining a router taking the target database as a main library as the target router.
7. The system according to claim 4, wherein the third determining unit is specifically configured to:
and selecting one of the databases deployed in the cloud as a target database according to a random principle, and determining a router taking the target database as a main database as a target router.
8. The system of claim 1, wherein the database deployed in the cloud is configured to synchronize, when a standby database in a router is accessed by an external service application, service data stored in correspondence with the external service application to a database in the router as a master database after interaction with the external service application is completed, and to purge the service data.
9. The system of claim 1, wherein the router is further configured to, after controlling the managed standby library to respond to the database access request, control the main library to respond to the database access request if it is monitored that the main library is currently in a normal operating state or is restored to a normal operating state from a downtime state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010164911.3A CN111400110B (en) | 2020-03-11 | 2020-03-11 | Database access management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010164911.3A CN111400110B (en) | 2020-03-11 | 2020-03-11 | Database access management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111400110A CN111400110A (en) | 2020-07-10 |
| CN111400110B true CN111400110B (en) | 2023-12-19 |
Family
ID=71430804
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010164911.3A Active CN111400110B (en) | 2020-03-11 | 2020-03-11 | Database access management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111400110B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114238521B (en) * | 2022-02-25 | 2022-06-24 | 梅州客商银行股份有限公司 | High-availability deployment method and device for bank core system database and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5999978A (en) * | 1997-10-31 | 1999-12-07 | Sun Microsystems, Inc. | Distributed system and method for controlling access to network resources and event notifications |
| CN104408174A (en) * | 2014-12-12 | 2015-03-11 | 用友软件股份有限公司 | Database routing device and method |
| CN105095317A (en) * | 2014-05-23 | 2015-11-25 | 中国银联股份有限公司 | Distributive database service management system |
| CN106294565A (en) * | 2016-07-27 | 2017-01-04 | 中国农业银行股份有限公司 | A kind of data bank access method and system |
| CN106503163A (en) * | 2016-10-31 | 2017-03-15 | 用友网络科技股份有限公司 | Based on the global configuration multi-tenant dynamic data origin system that SaaS is applied |
| CN107085570A (en) * | 2016-02-14 | 2017-08-22 | 华为技术有限公司 | Data processing method, application server and router |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10740353B2 (en) * | 2010-12-23 | 2020-08-11 | Mongodb, Inc. | Systems and methods for managing distributed database deployments |
| US9514160B2 (en) * | 2013-03-11 | 2016-12-06 | Oracle International Corporation | Automatic recovery of a failed standby database in a cluster |
| US10592528B2 (en) * | 2017-02-27 | 2020-03-17 | Sap Se | Workload capture and replay for replicated database systems |
-
2020
- 2020-03-11 CN CN202010164911.3A patent/CN111400110B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5999978A (en) * | 1997-10-31 | 1999-12-07 | Sun Microsystems, Inc. | Distributed system and method for controlling access to network resources and event notifications |
| CN105095317A (en) * | 2014-05-23 | 2015-11-25 | 中国银联股份有限公司 | Distributive database service management system |
| CN104408174A (en) * | 2014-12-12 | 2015-03-11 | 用友软件股份有限公司 | Database routing device and method |
| CN107085570A (en) * | 2016-02-14 | 2017-08-22 | 华为技术有限公司 | Data processing method, application server and router |
| CN106294565A (en) * | 2016-07-27 | 2017-01-04 | 中国农业银行股份有限公司 | A kind of data bank access method and system |
| CN106503163A (en) * | 2016-10-31 | 2017-03-15 | 用友网络科技股份有限公司 | Based on the global configuration multi-tenant dynamic data origin system that SaaS is applied |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111400110A (en) | 2020-07-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11360854B2 (en) | Storage cluster configuration change method, storage cluster, and computer system | |
| US10805406B2 (en) | Zone redundant computing services using multiple local services in distributed computing systems | |
| CN104486445B (en) | Distributed extendable resource monitoring system based on cloud platform | |
| US9454444B1 (en) | Using location tracking of cluster nodes to avoid single points of failure | |
| JP5047165B2 (en) | Virtualization network storage system, network storage apparatus and virtualization method thereof | |
| US7237027B1 (en) | Scalable storage system | |
| JP6190389B2 (en) | Method and system for performing computations in a distributed computing environment | |
| US7225356B2 (en) | System for managing operational failure occurrences in processing devices | |
| JP4515314B2 (en) | Computer system configuration reproduction method | |
| JP4727714B2 (en) | Server failover control method and apparatus, and computer system group | |
| US20130031229A1 (en) | Traffic reduction method for distributed key-value store | |
| US20090216986A1 (en) | Apparatus and method for managing logical volume in distributed storage systems | |
| CN109040212A (en) | Equipment access server cluster method, system, equipment and storage medium | |
| US10320905B2 (en) | Highly available network filer super cluster | |
| CN105095317A (en) | Distributive database service management system | |
| CN111966482B (en) | Edge computing system | |
| CN107180034A (en) | The group system of MySQL database | |
| CN109391487A (en) | A kind of configuration update method and system | |
| CN108462756A (en) | A kind of method for writing data and device | |
| CN111400110B (en) | Database access management system | |
| CN111274004A (en) | Process instance management method and device and computer storage medium | |
| JP2020191100A (en) | System, control method therefor, and program | |
| CN109005071B (en) | Decision deployment method and scheduling equipment | |
| JP2024514467A (en) | Geographically distributed hybrid cloud cluster | |
| CN112860480A (en) | Double-live storage system and data processing method thereof |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220914 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |