Shulou(Shulou.com)05/31 Report--

I believe that many inexperienced people have no idea about what MySQL middleware is like. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

First of all, the basis of the development of database technology is to achieve the relevant technical guarantee under the background of business promotion. The improvement of business requirements will inevitably have higher requirements in terms of data volume and access volume, while mapping to the database level is not a simple expansion and addition of resources, we sometimes need more flexibility, rapid implementation, and higher performance. These are the problems in front of us, not just the DBA team.

So many early databases, from one master one slave, one master multi-slave architecture, gradually evolved to read-write separation, sub-database sub-table, and then distributed. At the same time, from many levels, the solutions in the industry really blossom. I remember talking to my colleagues a few days ago, saying, if you compare Oracle and MySQL, what do you want me to say? I said that simply evaluating the performance and function of a single machine, MySQL lags far behind, but in terms of cost, technology control and customization, MySQL's simplicity has become one of its advantages. On this basis, it has a lot of open source solutions. These make the original MySQL applications become very rich. Do you think MySQL can do enterprise-level solutions? if you look at the usage scenarios of BAT, you can still stand the test. Note that the usage scenarios I am talking about here are not one-size-fits-all scenarios.

Back to the point, there are actually a lot of MySQL middleware, official open source, let's briefly say that there are still many solutions in the industry, some of which have not been investigated yet and have not been put forward in the article in time.

Let's start with what MySQL middleware can do. To answer this question, we can ask a reverse question about what bottlenecks the database will have as business requirements change, such as:

1. A single server cannot carry the existing pressure

two。 The single table capacity of the database is getting larger and larger.

3. A large number of reading and writing needs can not be balanced.

4. If the capacity of resources is expanded, the application will be changed greatly.

5. The load of resources cannot be split, or it is not easy to split.

Therefore, many database middleware on the market mainly share most or part of the function points.

Dong Hongyu of Waldorf Technology summed up a good picture. I took it directly.

We will basically discuss the following middleware, some of which are not in the above figure and will be added.

MySQL Fabric, MySQL Router,MySQL Proxy

Fabric can provide MySQL's HA and Sharding solutions. MySQL Router is a lightweight middleware used to achieve highly available and scalable functions. MySQL Fabric can achieve high availability and extended functions at the driver level, and the application side is needed to adapt to the transformation. The access protocol of MySQL Router middleware is the same as that of MySQL, and the application does not need to be modified. MySQL Router is used as a "troika" in InnoDB Cluster recently launched by MySQL. The lonely one is MySQL proxy, which can no longer be downloaded. Since its launch, it has mainly been a test version, so there are still some problems in many functions.

360 Atlas

This is a middleware scheme launched by domestic company 360. the address of github is https://github.com/Qihoo360/Atlas.

In the case of github, the star rating is quite high, and the latest maintenance was 4 days ago. It is designed on the basis of mysql-proxy 0.8.2, optimized and added some new features.

Mycat

This is also a domestic middleware solution, which is popular in the industry. The official link is: http://www.mycat.io/

There is also a Mycat-related book, distributed Database Architecture and Enterprise practice-- based on Mycat Middleware

As far as I know, he mainly supports MySQL, but also supports other databases, such as Oracle, etc., which is also done by a wave of friends.

One of the reasons I like it better is that it is open source, and the source code is Java.

Oneproxy

This is the former Alipay architect building chief development, currently supports multi-database, based on MySQL official proxy ideas using c to develop, OneProxy is a commercial charge for middleware, focusing on performance and stability, is commercially paid.

DRDS

Ali distributed Relational Database Service (Distribute Relational Database Service, referred to as DRDS) is an online distributed database service with horizontal split, smooth expansion and reduction, and separation of read and write. Formerly known as Taobao TDDL, and before that there was Cobar, no longer maintained.

The picture is from: http://blog.csdn.net/jerome_s/article/details/53966569

Vitess

Google developed database middleware, cluster based on ZooKeeper management, through RPC data processing official website is very brief: http://vitess.io/ open is a big V

Maxscale

MaxScale is developed by mariadb, the current version does not support sub-database and sub-table, in several other aspects are very good. The github link is: https://github.com/mariadb-corporation/MaxScale

After reading the above, have you mastered the method of MySQL middleware? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.