WO2019061657A1

WO2019061657A1 - Data service method and system

Info

Publication number: WO2019061657A1
Application number: PCT/CN2017/108745
Authority: WO
Inventors: 刘洋; 李鹃; 付士元; 王浩
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-09-30
Filing date: 2017-10-31
Publication date: 2019-04-04
Also published as: CN107734017B; CN107734017A

Abstract

Disclosed in the present application are a data service method and system. The method comprises: a distributing device receives an access request of a client; the distributing device distributes the access request to one of a first data center and a second data center according to a preset distributing rule; the data center receiving the access request in the first data center and the second data center feeds back a corresponding data resource to the client according to the access request. By means of the present application, service and distributing control can be provided for a client at the same time by means of double data centers; the high availability of the data service system is guaranteed; and the reliability of the data service system is enhanced.

Description

Data service method and system

This application is based on the priority of the Paris Convention on the application of the Chinese Patent Application No. CN 201710915082.6, entitled "Data Service Method and System", filed on September 30, 2017, the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of computer technologies, and in particular, to a data service method and system.

Background technique

The existing data service system generally only includes one data center. For the data service system of such a single data center, once the data center is abnormal, the data service system cannot be continuously available, thereby making the reliability of the data service system more reliable. low.

Summary of the invention

The present application provides a data service method and system, which aims to ensure the continuous availability of a data service system and improve the reliability of a data service system.

To achieve the above objective, a data service system provided by the first aspect of the present application, the data service system includes a flow dividing device, a first data center, and a second data center; data resources and second data of the first data center The data resources of the center are synchronized in real time;

The offloading device receives an access request of a client;

The offloading device offloads the access request to one of the first data center and the second data center according to a preset offloading rule;

The data center that receives the access request in the first data center and the second data center feeds back corresponding data resources to the client according to the access request.

In addition, to achieve the above object, the second aspect of the present application further provides a data service method, which is applied to the data service system as described above, where the data service method includes:

The offloading device receives the access request of the client;

And the data center that receives the access request in the first data center and the second data center feeds back corresponding data resources to the client according to the access request;

The data resource of the first data center and the data resource of the second data center are synchronized in real time.

The data service method and system provided by the present application distributes the received access request of the client to the first data center in the data service system according to a preset offloading rule. Any one of the second data centers, and any data center that receives the access request in the data service system may feed back corresponding data resources to the client according to the access request, thereby implementing The dual data center provides services and shunt control for the client at the same time. Further, the databases of the two data centers in the data service system can realize real-time synchronization in different places. On the one hand, the full use of resources avoids the waste of a data center being idle for many years, and doubles the data service capability through resource integration; on the other hand, if one of the data centers is abnormal, the client's access request can be dynamically updated. Switching to another normal running data center is non-aware to the user, ensuring high availability of the data service system and improving the reliability of the data service system.

DRAWINGS

1 is a schematic structural diagram of an embodiment of a data service system according to the present application;

2 is a schematic structural diagram of another embodiment of a data service system according to the present application;

3 is a partial schematic structural diagram of a database in a data service system of the present application;

4 is a schematic diagram of another partial architecture in a database in the data service system of the present application;

FIG. 5 is a schematic flowchart of an embodiment of a data service method according to an application of the present application.

Detailed ways

In order to make the technical problems, technical solutions and beneficial effects to be solved by the present application clearer and clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

The application provides a data service system. 1 is a schematic structural diagram of a preferred embodiment of a data service system 10 of the present application.

In this embodiment, the data service system 10 may include, but is not limited to, a first data center 11, a second data center 12, and a shunt device (not shown).

The first data center 11 and the second data center 12 in FIG. 1 can be respectively constructed in different geographical locations. For example, the first data center 11 is in Shenzhen and the second data center 12 is in Shanghai. The client 13 in FIG. 1 is connected to the first data center 11 and the second data center 12 via a network.

In an embodiment, as shown in FIG. 1, the first data center 11 may include a first server 111 and a first memory 112 for storing data resources, and the second data center 12 may include a second server 121 and for storing A second memory 122 of the data resource. Both the first memory 112 and the second memory 122 can be network memories. The first server 111 and the second server 121 are respectively connected to the network. The first server 111 is connected to the first memory 112, and the second server 121 is connected to the second memory 122. First server 111 and second server 121 Can be configured based on F5 VS/iRULES, nginx+php, tomcat.

In another embodiment, as shown in FIG. 2, the first data center 11 may include a first server 111 and a database, and the second data center 12 may include a second server 121 and a database. The first server 111 and the second server 121 are respectively connected to the network.

The offloading device receives the access request of the client 13, and offloads the access request to one of the first data center 11 and the second data center 12 according to a preset offloading rule.

In an optional embodiment, the offloading device can be independently configured in a background server of the network or system, and the shunt device is connected to the first data center 11 and the second data center 12, respectively. Specifically, the shunt device is connected to the first server 111 and the second server 121, respectively. After receiving the access request from the client 13, the offloading device determines the data center corresponding to the access request according to the preset offloading rule, and forwards the access request to the determined data center through the network.

Alternatively, in another alternative embodiment, the shunt device can also be configured in the first data center 11 and/or the second data center 12. For example, the shunt device is the first server 111 and the second server 121 described above. The access request sent by the client 13 is sent to the first server 111 and the second server 121 via the network, and the first server 111 and the second server 121 respectively determine whether they respond to the access request according to a preset offload rule. It can be understood that the preset shunting rule enables at least one of the first server 111 and the second server 121 to respond to the access request. The preset offloading rule enables one of the first server 111 and the second server 121 to respond to the access request.

The offloading device may use the GTM mechanism to offload the access request of the client 13. The preset offload rule can be in the following manner:

Method 1, the proportional offload method: the ratio between the number of access requests that are offloaded to the first data center 11 and the number of access requests that are offloaded to the second data center 12 is a preset ratio;

For example, the ratio of the number of access requests that are offloaded to the first data center 11 to the number of access requests that are offloaded to the second data center 12 may be X:Y. Where X and Y are both positive integers. Therefore, the number of access requests responded to by the two data centers can be reasonably allocated, and the resources can be reasonably utilized, thereby avoiding a waste of resources in a data center that is idle for a long time, and improving data service capabilities through resource integration.

Method 2, the geographical branching method: performing traffic distribution according to the geographic location where the client 13 of the access request is located;

The correspondence between the geographic location and the data center can be set in advance. For example, the geographic location corresponding to the first data center 11 may be Nanjing, Beijing, Hangzhou, and the like. The geographic location corresponding to the second data center 12 may be Shenzhen, Guangzhou, Xiamen, and the like. For the access request sent by the client 13 of Nanjing, according to the correspondence, the first data center 11 responds, and the access request is offloaded to the first data center 11. Sent to the client 13 in Shenzhen The access request is responded to by the second data center 12 according to the correspondence, and the access request is offloaded to the second data center 12.

Alternatively, the correspondence may be established according to the principle of proximity. The geographic location of the data center can be close to the location of the data center.

The method can allocate the access requests responded by the two data centers according to the geographical reason, so that the client 13 can access the data center nearby, utilize resources more reasonably, and improve the data service capability through resource integration.

Mode 3: When an abnormality occurs in one of the first data center 11 and the second data center 12, the access request is offloaded to a data center where no abnormality occurs.

For example, if an abnormality occurs in the first data center 11, all access requests are offloaded to the second data center 12. The switching of the offload is not perceptible to the client 13, thereby ensuring high availability of the data service system.

The data center receiving the access request in the first data center 11 and the second data center 12 feeds back corresponding data resources to the client 13 according to the access request.

The following takes the access request by the first data center 11 as an example:

For the data service system shown in FIG. 1, the first server 111 receives the access request. The first server 111 reads data from the first memory 112 via NFS according to the access request, and feeds back to the client 13 that initiated the access request.

For the data service system shown in FIG. 2, the first server 111 receives the access request. The first server 111 reads data from the database according to the access request and feeds back to the client 13 that initiated the access request.

The data resources of the first data center 11 and the data resources of the second data center 12 are synchronized in real time.

For the data service system shown in FIG. 1, when the data stored in the first memory 112 changes, the first server 111 synchronizes the data resources in the first memory 112 to the second memory 122. Specifically, the first server 111 can synchronize the data resources in the first memory 112 to the second memory 122 in real time and remotely through a data mirror backup tool (such as remote synchronize).

By adopting the above synchronization strategy, it is possible to effectively ensure that when an abnormality occurs in one of the data centers, the access request can be offloaded to the data center that is working normally. The switching of the offload is non-aware to the client 13, ensuring high availability of the data service system.

For the data service system shown in Figure 2, its database has the following two implementations:

Embodiment 1, as shown in FIG. 2, the first data center 11 includes a first database 113 and a second database 114 for storing the data resources, and the second data center 12 includes a data for storing the data. The third database 123 and the fourth database 124 of resources.

The first database 113 and the third database 123 may be Redis databases, using "main + From the "mode schema. The first database 113 includes a first primary database and a first secondary database. The third database 123 includes a third primary database and a third secondary database.

As shown in FIG. 3, the second database 114 and the fourth database 124 may be Mysql databases, the second database 114 employs a "master + slave" mode architecture, and the fourth database 124 employs a "slave + slave" mode architecture. The second database 114 includes a second primary database and a second secondary database, and the fourth database 124 includes two fourth secondary databases.

The second database 114 synchronizes the data resources to the fourth database 124 via the sql statement.

In the first data center 11, the first server 111 can perform read and write operations on the first database 113 and the second database 114. In the second data center 12, the second server 121 can perform a read operation on the third database 123 and the fourth database 124.

The data resources in the first database 113 are synchronized with the data resources in the second database 114 in real time; the data resources in the third database 123 are synchronized with the data resources in the fourth database 124 in real time;

The data resources in the first primary database are synchronized with the data resources in the first slave database in real time; the data resources in the third primary database are synchronized with the data resources in the third slave database in real time;

The data resources in the second primary database are synchronized with the data resources in the second slave database in real time; the data resources in the second primary database are synchronized in real time to one of the fourth databases 124 From the database, the data resources in the second slave database are synchronized in real time to another of the fourth slave databases in the fourth database 124.

By setting a plurality of databases in both the first data center 11 and the second data center 12, and adopting the above synchronization strategy, it is possible to effectively ensure that when an abnormality occurs in one of the data centers, the access request can be offloaded to the data center that is working normally. The switching of the offload is non-aware to the client 13, ensuring high availability of the data service system.

Embodiment 2, as shown in FIG. 2, the first data center 11 includes a first database 113 and a second database 114 for storing the data resources, and the second data center 12 includes a data for storing the data. The third database 123 and the fourth database 124 of resources.

The first database 113 and the third database 123 may be Redis databases, employing a "master + slave" mode architecture. The first database 113 includes a first primary database and a first secondary database. The third database 123 includes a third primary database and a third secondary database.

As shown in FIG. 4, the second database 114 and the fourth database 124 may be an Oracle database, the second database 114 adopts a "master + slave" mode architecture, and the fourth database 124 employs a "master + slave" mode architecture. The second database 114 includes a second primary database and a second secondary database, and the fourth database 124 includes a fourth primary database and a fourth secondary database.

The second database 114 synchronizes the data to the fourth database 124 via DataGuard data synchronization technology.

In the first data center 11, the first server 111 pairs the first database 113 and the second data Library 114 can perform read and write operations. In the second data center 12, the second server 121 can perform a read operation on the third database 123 and the fourth database 124.

The data resources in the second primary database are synchronized with the data resources in the second slave database in real time; the data resources in the fourth primary database are synchronized with the data resources in the fourth slave database in real time; The data resources in the second primary database are synchronized in real time to the fourth primary database.

The data service system of this embodiment offloads the access request to one of the first data center 11 and the second data center 12 according to a preset offloading rule by receiving the access request of the client 13 And the data center that receives the access request in the first data center 11 and the second data center 12 feeds back the corresponding data resource to the client 13 according to the access request, so that the data center can be implemented through the dual data center. Off-site applications provide services, offload control, and read-write separation, and the databases in the two data centers can be synchronized in real time. On the one hand, the full use of resources avoids the waste of a data center being idle for many years, and doubles the data service capability through resource integration; on the other hand, if one of the data centers is abnormal, the GTM mechanism can detect it in real time. Abnormally, the user's access request is dynamically switched to another normal running data center, which is non-aware to the user, guarantees high availability for the data service system, and improves the reliability of the data service system.

The application further provides a data service method. The data service method is implemented based on the data service system described in the foregoing embodiment. For details of the data service system, reference may be made to the foregoing embodiments, and details are not described herein.

Referring to FIG. 5, FIG. 5 is a schematic flowchart of an embodiment of a data service method according to an application.

In an embodiment, the data service method comprises:

Step S10: The offloading device receives an access request of the client.

Step S20: The offloading device offloads the access request to one of the first data center and the second data center according to a preset offloading rule.

In an optional embodiment, the shunt device can be independently configured on a network or a system. The back-end server is connected to the first data center and the second data center. Specifically, the shunt device is respectively connected to the first server and the second server. After receiving the access request from the client, the traffic distribution device determines the data center corresponding to the access request according to the preset traffic distribution rule, and forwards the access request to the determined data center through the network.

Alternatively, in another optional embodiment, the shunt device may also be configured in the first data center and/or the second data center. For example, the shunt device is the first server and the second server. The access request sent by the client is sent to the first server and the second server respectively via the network, and the first server and the second server respectively determine whether they respond to the access request according to the preset offload rule. It can be understood that the preset shunting rule enables at least one of the first server and the second server to respond to the access request. The preset offloading rule enables one of the first server and the second server to respond to the access request.

The offloading device may use a GTM mechanism to offload client access requests. The preset offload rule can be in the following manner:

Method 1, the proportional offload method: the ratio between the number of access requests that are offloaded to the first data center and the number of access requests that are offloaded to the second data center is a preset ratio;

For example, the ratio of the number of access requests diverted to the first data center to the number of access requests diverted to the second data center may be X:Y. Where X and Y are both positive integers. Therefore, the number of access requests responded to by the two data centers can be reasonably allocated, and the resources can be reasonably utilized, thereby avoiding a waste of resources in a data center that is idle for a long time, and improving data service capabilities through resource integration.

Method 2, the geographical branching method: performing traffic distribution according to the geographical location of the client where the access request is located;

The correspondence between the geographic location and the data center can be set in advance. For example, the geographic location corresponding to the first data center may be Nanjing, Beijing, Hangzhou, and the like. The geographic location corresponding to the second data center may be Shenzhen, Guangzhou, Xiamen, and the like. For the access request sent by the client of Nanjing, according to the correspondence, the first data center responds, and the access request is offloaded to the first data center. For the access request sent by the client in Shenzhen, according to the correspondence, the second data center responds, and the access request is offloaded to the second data center.

In this way, the access requests responded by the two data centers can be allocated according to the geographical location, so that the client can access the data center nearby, utilize resources more rationally, and improve data service capability through resource integration.

Mode 3: When an abnormality occurs in one of the first data center and the second data center, the access request is offloaded to a data center where no abnormality occurs.

For example, if an exception occurs in the first data center, all access requests are offloaded to the second data center. The switching of the offload is non-aware to the client, thereby ensuring high availability of the data service system.

Step S30: The data center that receives the access request in the first data center and the second data center feeds back corresponding data resources to the client according to the access request.

The following takes the access request as an example in the first data center:

For the data service system shown in FIG. 1, the first server receives the access request. The first server reads data from the first memory through NFS according to the access request, and feeds back to the client that initiated the access request.

For the data service system shown in FIG. 2, the first server receives the access request. The first server reads data from the database according to the access request and feeds back to the client that initiated the access request.

The data resources of the first data center and the data resources of the second data center are synchronized in real time.

The data service method of this embodiment, by accessing the received access request of the client according to a preset offloading rule, to the one of the first data center and the second data center, and the The data center that receives the access request in the first data center and the second data center feeds back the corresponding data resource to the client according to the access request, so that the dual data center can realize the off-site application and provide the service and the offload simultaneously. Control and read-write separation, and the database of the two data centers can achieve real-time synchronization in different places. On the one hand, the full use of resources avoids the waste of a data center being idle for many years, and doubles the data service capability through resource integration; on the other hand, if one of the data centers is abnormal, the GTM mechanism can detect it in real time. Abnormally, the user's access request is dynamically switched to another normal running data center, which is non-aware to the user, guarantees high availability for the data service system, and improves the reliability of the data service.

Further, in the data service system shown in FIG. 1, in an optional embodiment, based on the foregoing embodiment, the method further includes: when the data stored in the first memory changes, A server synchronizes data resources in the first memory to a second memory. Specifically, the first server may synchronize the data resources in the first memory to the second memory in real time through a data mirror backup tool (such as remote synchronize).

By adopting the above synchronization strategy, it is possible to effectively ensure that when an abnormality occurs in one of the data centers, the access request can be offloaded to the data center that is working normally. The switching of the offload is non-aware to the client, ensuring high availability of the data service system.

Further, for the data service system shown in FIG. 2, in an optional embodiment, based on the above embodiments, the database has the following two implementation manners:

Embodiment 1, as shown in FIG. 2, the first data center includes a first database and a second database for storing the data resource, and the second data center includes a third for storing the data resource. Database and fourth database.

The first database and the third database may be Redis databases, using a "master + slave" mode architecture. The first database includes a first primary database and a first secondary database. The third database includes a third primary database and a third secondary database.

As shown in FIG. 3, the second database and the fourth database may be Mysql databases, the second database adopts a "master + slave" mode architecture, and the fourth database adopts a "slave + slave" mode architecture. The second database includes a second primary database and a second secondary database, and the fourth database includes two fourth secondary databases.

The second database synchronizes the data resources to the fourth database through the sql statement.

In the first data center, the first server can perform read and write operations on the first database and the second database. In the second data center, the second server can perform read operations on the third database and the fourth database.

The data service method further includes:

The data resources in the first database are synchronized with the data resources in the second database in real time; the data resources in the third database are synchronized with the data resources in the fourth database in real time;

The data resources in the second primary database are synchronized with the data resources in the second slave database in real time; the data resources in the second primary database are synchronized in real time to one of the fourth slaves in the fourth database In the database, the data resources in the second slave database are synchronized in real time to another fourth slave database in the fourth database.

By setting a plurality of databases in both the first data center and the second data center, and adopting the above synchronization strategy, it is possible to effectively ensure that when an abnormality occurs in one of the data centers, the access request can be offloaded to the data center that works normally. The switching of the offload is non-aware to the client, ensuring high availability of the data service system.

Embodiment 2, as shown in FIG. 2, the first data center includes a first database and a second database for storing the data resource, and the second data center includes a third for storing the data resource Database and fourth database.

As shown in FIG. 4, the second database and the fourth database may be an Oracle database, and second The database adopts the "master + slave" mode architecture, and the fourth database adopts the "master + slave" mode architecture. The second database includes a second primary database and a second secondary database, and the fourth database includes a fourth primary database and a fourth secondary database.

The second database synchronizes the data to the fourth database via DataGuard data synchronization technology.

The data service method further includes:

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and can also be implemented by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM, including a number of instructions to make a terminal device (can be a mobile phone, computer, server, air conditioner, or network) The network device, etc.) performs the methods described in the various embodiments of the present application.

The preferred embodiments of the present application have been described above with reference to the drawings, and are not intended to limit the scope of the application. The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments. Additionally, although logical sequences are shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.

A person skilled in the art can implement the present application in various variants without departing from the scope and spirit of the present application. For example, the features of one embodiment can be used in another embodiment to obtain another embodiment. Any modifications, equivalent substitutions and improvements made within the technical concept of the application should be within the scope of the application.

Claims

A data service system, comprising: a data distribution system, a first data center and a second data center; and the data resources of the first data center and the data resources of the second data center are synchronized in real time;

The offloading device receives an access request of a client;

The offloading device offloads the access request to one of the first data center and the second data center according to a preset offloading rule;

The data center that receives the access request in the first data center and the second data center feeds back corresponding data resources to the client according to the access request.
The data service system according to claim 1, wherein the preset offloading rule is:

The ratio between the number of access requests that are offloaded to the first data center and the number of access requests that are offloaded to the second data center is a preset ratio.
The data service system according to claim 1, wherein the preset offloading rule is:

The location of the client according to the access request is distributed nearby.
The data service system according to claim 1, wherein the preset offloading rule is:

When an abnormality occurs in one of the first data center and the second data center, the access request is offloaded to a data center where no abnormality has occurred.
The data service system of claim 1 wherein said first data center comprises a first memory for storing said data resource and a first server coupled to said first memory, said second The data center includes a second memory for storing the data resource; the first memory and the second memory are both network memories;

The first server synchronizes data resources in the first memory to the second memory when a data resource in the first memory changes.
A data service system according to claim 2, wherein said first data center includes a first database and a second database for storing said data resources, said data resources in said first database and said The data resources in the second database are synchronized in real time;

The second data center includes a third database and a fourth database for storing the data resources, and the data resources in the third database are synchronized with the data resources in the fourth database in real time;

The first database and the third database are Redis databases, and the second database and the fourth database are Mysql databases, wherein:

The first database includes a first primary database and a first secondary database, and the data resources in the first primary database are synchronized with the data resources in the first secondary database in real time;

The third database includes a third primary database and a third secondary database, and the data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The second database includes a second primary database and a second secondary database, and the data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The fourth database includes two fourth slave databases, and the data resources in the second master database are synchronously synchronized to one of the fourth slave databases in the fourth database, and the second slave database The data resource is synchronized in real time to another of the fourth slave databases in the fourth database.
A data service system according to claim 3, wherein said first data center includes a first database and a second database for storing said data resources, said data resources in said first database and said The data resources in the second database are synchronized in real time;

The second data center includes a third database and a fourth database for storing the data resources, and the data resources in the third database are synchronized with the data resources in the fourth database in real time;

The first database and the third database are Redis databases, and the second database and the fourth database are Mysql databases, wherein:

The first database includes a first primary database and a first secondary database, and the data resources in the first primary database are synchronized with the data resources in the first secondary database in real time;

The third database includes a third primary database and a third secondary database, and the data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The second database includes a second primary database and a second secondary database, and the data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The fourth database includes two fourth slave databases, and the data resources in the second master database are synchronously synchronized to one of the fourth slave databases in the fourth database, and the second slave database The data resource is synchronized in real time to another of the fourth slave databases in the fourth database.
A data service system according to claim 4, wherein said first data center includes a first database and a second database for storing said data resources, said data resources in said first database and said The data resources in the second database are synchronized in real time;

The second data center includes a third database for storing the data resources and a fourth database, wherein the data resources in the third database are synchronized with the data resources in the fourth database in real time;

The first database and the third database are Redis databases, and the second database and the fourth database are Mysql databases, wherein:

The first database includes a first primary database and a first secondary database, and the data resources in the first primary database are synchronized with the data resources in the first secondary database in real time;

The third database includes a third primary database and a third secondary database, and the data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The second database includes a second primary database and a second secondary database, and the data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The fourth database includes two fourth slave databases, and the data resources in the second master database are synchronously synchronized to one of the fourth slave databases in the fourth database, and the second slave database The data resource is synchronized in real time to another of the fourth slave databases in the fourth database.
A data service system according to claim 2, wherein said first data center includes a first database and a second database for storing said data resources, said data resources in said first database and said The data resources in the second database are synchronized in real time;

The second data center includes a third database and a fourth database for storing the data resources, and the data resources in the third database are synchronized with the data resources in the fourth database in real time;

The first database and the third database are Redis databases, and the second database and the fourth database are Oracle databases, wherein:

The first database includes a first primary database and a first secondary database, and the data resources in the first primary database are synchronized with the data resources in the first secondary database in real time;

The third database includes a third primary database and a third secondary database, and the data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The second database includes a second primary database and a second secondary database, and the data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The fourth database includes a fourth primary database and a fourth secondary database, and the data resources in the fourth primary database are synchronized with the data resources in the fourth secondary database in real time;

The data resources in the second primary database are synchronized in real time to the fourth primary database.
A data service system according to claim 3, wherein said first data center includes a first database and a second database for storing said data resources, said data resources in said first database and said The data resources in the second database are in real time step;

The second data center includes a third database and a fourth database for storing the data resources, and the data resources in the third database are synchronized with the data resources in the fourth database in real time;

The first database and the third database are Redis databases, and the second database and the fourth database are Oracle databases, wherein:

The first database includes a first primary database and a first secondary database, and the data resources in the first primary database are synchronized with the data resources in the first secondary database in real time;

The third database includes a third primary database and a third secondary database, and the data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The second database includes a second primary database and a second secondary database, and the data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The fourth database includes a fourth primary database and a fourth secondary database, and the data resources in the fourth primary database are synchronized with the data resources in the fourth secondary database in real time;

The data resources in the second primary database are synchronized in real time to the fourth primary database.
A data service system according to claim 4, wherein said first data center includes a first database and a second database for storing said data resources, said data resources in said first database and said The data resources in the second database are synchronized in real time;

The second data center includes a third database and a fourth database for storing the data resources, and the data resources in the third database are synchronized with the data resources in the fourth database in real time;

The first database and the third database are Redis databases, and the second database and the fourth database are Oracle databases, wherein:

The first database includes a first primary database and a first secondary database, and the data resources in the first primary database are synchronized with the data resources in the first secondary database in real time;

The third database includes a third primary database and a third secondary database, and the data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The second database includes a second primary database and a second secondary database, and the data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The fourth database includes a fourth primary database and a fourth secondary database, and the data resources in the fourth primary database are synchronized with the data resources in the fourth secondary database in real time;

The data resources in the second primary database are synchronized in real time to the fourth primary database.
A data service method applied to a data service system, characterized in that The data service methods include:

The offloading device receives the access request of the client;

The offloading device offloads the access request to one of the first data center and the second data center according to a preset offloading rule;

And the data center that receives the access request in the first data center and the second data center feeds back corresponding data resources to the client according to the access request;

The data resource of the first data center and the data resource of the second data center are synchronized in real time.
The data service method according to claim 12, wherein the preset offloading rule is:

The ratio between the number of access requests that are offloaded to the first data center and the number of access requests that are offloaded to the second data center is a preset ratio.
The data service method according to claim 12, wherein the preset offloading rule is:

The location of the client according to the access request is distributed nearby.
The data service method according to claim 12, wherein the preset offloading rule is:

When an abnormality occurs in one of the first data center and the second data center, the access request is offloaded to a data center where no abnormality has occurred.
The data service method according to claim 12, wherein said first data center includes a first memory for storing said data resource and a first server connected to said first memory, said second The data center includes a second memory for storing the data resource; the first memory and the second memory are both network memories; and the data service method further includes:

The first server synchronizes data resources in the first memory to the second memory when a data resource in the first memory changes.
The data service method according to claim 13, wherein said first data center includes a first database and a second database for storing said data resources, said second data center including said a third database and a fourth database of data resources, the first database and the third database are Redis databases, the second database and the fourth database are Mysql databases; the first database includes a first primary database and a first database From the database, the third database includes a third primary database and a third secondary database, the second database includes a second primary database and a second secondary database, the fourth database includes two fourth secondary databases, Data service methods also include:

The data resources in the first database are synchronized with the data resources in the second database in real time;

The data resources in the third database are synchronized with the data resources in the fourth database in real time;

The data resources in the first primary database are synchronized with the data resources in the first slave database in real time;

The data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The data resources in the second primary database are synchronously synchronized to one of the fourth slave databases in the fourth database, and the data resources in the second slave database are synchronized in real time to another one in the fourth database. One of the fourth slave databases.
The data service method according to claim 14, wherein said first data center includes a first database and a second database for storing said data resources, said second data center including said a third database and a fourth database of data resources, the first database and the third database are Redis databases, the second database and the fourth database are Mysql databases; the first database includes a first primary database and a first database From the database, the third database includes a third primary database and a third secondary database, the second database includes a second primary database and a second secondary database, the fourth database includes two fourth secondary databases, Data service methods also include:

The data resources in the first database are synchronized with the data resources in the second database in real time;

The data resources in the third database are synchronized with the data resources in the fourth database in real time;

The data resources in the first primary database are synchronized with the data resources in the first slave database in real time;

The data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The data resources in the second primary database are synchronously synchronized to one of the fourth slave databases in the fourth database, and the data resources in the second slave database are synchronized in real time to another one in the fourth database. One of the fourth slave databases.
The data service method according to claim 15, wherein said first data center includes a first database and a second database for storing said data resources, The second data center includes a third database and a fourth database for storing the data resource, the first database and the third database are Redis databases, and the second database and the fourth database are Mysql databases; The first database includes a first primary database and a first secondary database, the third database includes a third primary database and a third secondary database, and the second database includes a second primary database and a second secondary database, the first database The four databases include two fourth slave databases, and the data service methods further include:

The data resources in the first database are synchronized with the data resources in the second database in real time;

The data resources in the third database are synchronized with the data resources in the fourth database in real time;

The data resources in the first primary database are synchronized with the data resources in the first slave database in real time;

The data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The data resources in the second primary database are synchronously synchronized to one of the fourth slave databases in the fourth database, and the data resources in the second slave database are synchronized in real time to another one in the fourth database. One of the fourth slave databases.
The data service method according to claim 13, wherein said first data center includes a first database and a second database for storing said data resources, said second data center including said a third database and a fourth database of data resources, the first database and the third database are Redis databases, the second database and the fourth database are Oracle databases, and the first database includes a first primary database and a first database From the database, the third database includes a third primary database and a third secondary database, the second database includes a second primary database and a second secondary database, and the fourth database includes a fourth primary database and a fourth secondary database The data service method further includes:

The data resources in the first database are synchronized with the data resources in the second database in real time;

The data resources in the third database are synchronized with the data resources in the fourth database in real time;

The data resources in the first primary database are synchronized with the data resources in the first slave database in real time;

The data resources in the third primary database are synchronized with the data resources in the third secondary database in real time;

The data resources in the second primary database are synchronized with the data resources in the second secondary database in real time;

The data resources in the fourth primary database are synchronized with the data resources in the fourth secondary database in real time, and the data resources in the second primary database are synchronized in real time to the fourth primary database.