Data storage and query method based on distributed database

Abstract

The invention discloses a data storage and query method based on a distributed database, and the method comprises the following steps: S1, setting a connected data source through a client, and determining the data type of to-be-processed data; S2, determining that the data is core business data, and storing the core business data in an ORACLE database; s3, confirming that the data is log data, andasynchronously storing the log data into a MySQL database at the rear end of the database middleware through a message queue; s4, storing the database middleware the data to fragmentation nodes of aMySQL database main library; and S5, enabling the MySQL database main library to regularly extract the data of each fragment node and synchronizes the data to a historical database. The message queueasynchronously lands the log service data into the log data center library, so that the data volume of the core transaction library is reduced, the performance of the core service library is guaranteed, and the overall operation efficiency of core services is improved. Meanwhile, the query and storage problems of log historical data are efficiently solved.

Description

technical field [0001] The invention relates to a data storage method, in particular to a data storage and query method based on a distributed database. Background technique [0002] At present, the ORACLE database deployment method mainly adopts the traditional C / S or B / S architecture. Whether it is based on the client or the browser, the dependence on the core database has not changed. However, due to the continuous accumulation of database storage data volume, In addition, the number of core database transactions and historical data (such as business report data and non-core business data) are stored interactively and mixed, which leads to lower and lower business processing performance, and it becomes relatively more difficult to expand horizontally, which can easily lead to database performance. problems and failures that affect business continuity. The prior art has the following shortcomings: [0003] 1. The traditional ORACLE database cannot be effectively scaled h...

AI Technical Summary

Problems solved by technology

[0003] 1. The traditional ORACLE database cannot be effectively expanded horizontally: the horizontal dismantling of the ORACLE database needs to evaluate the business impact, and the application comprehensive test after the dismantling of the database is carried out in the test environment. There is a shutdown window for data cutover and cutover to complete the business trial. run, time consuming

[0004] 2. No separation of data reading and writing: With the continuous expansion of business and the continuous increase of data, the pressure on the database will also increase. The basic optimization of the database or SQL cannot achieve the final effect. At this time, the separation of reading and writing is adopted. Strategy to change the status quo is a necessary choice. The application scenarios of traditional ORACLE databases do not use the read-write separation technology of the database.

[0005] 3. The core transaction data and log data are mixed and stored without data stripping, resulting in low data processing performance

Images