Shulou(Shulou.com)06/01 Report--

What is the horizontal split in the database? Many novices are not very clear about this. In order to help you solve this problem, the following editor will explain it in detail. People with this need can come and learn. I hope you can gain something.

If you encounter a stand-alone bottleneck after vertical split, you can use horizontal split.

The difference compared to vertical split is:

Vertical split is to split different tables into different databases, while horizontal split is to split the same table into different databases.

Compared with vertical split, horizontal split is not to classify the data of a table, but to spread it into multiple libraries according to some rules of a field, and each table contains part of the data. To put it simply, we can understand the horizontal segmentation of data as the segmentation of data rows, that is, some rows in the table are split into a database, while other rows are split into other databases. There are two modes: sub-table and sub-database.

The advantages are:

The splitting rules are abstract, and the join operation can basically be done in the database.

There is no performance bottleneck of single library big data and high concurrency.

The modification of the application side is less.

The stability and load capacity of the system are improved.

The disadvantages are:

Split rules are difficult to abstract.

The consistency of fragmented transactions is difficult to solve.

It is difficult to expand the data many times and has a great amount of maintenance.

Cross-library join has poor performance.

Split principle

1. Try not to split up, the architecture is evolved, not overnight. (SOA)

two。 Find the most suitable segmentation dimension as much as possible.

3. As database middleware is difficult to grasp the advantages and disadvantages of data Join implementation, and it is extremely difficult to achieve high performance, business reading as little as possible using multi-table Join-through data redundancy as far as possible, grouping to avoid data collapse of database multi-table join.

4. Try to avoid distributed transactions.

5. The single table is split into data less than 10 million.

Syncopation scheme

Range, enumeration, time, modularization, hash, assignment, etc.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.