About MySQL Fabric

Fabric is one of Oracle's main pushes, implementing two main things in MySQL architecture design:

1. High Availability

2. Sharding (based on HA Group)

Borrow a map from the web, familiar with high-availability and Atlas and other open-source sharding scheme of students at a glance to know what the meaning.

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/80/30/wKioL1c6z0-TFfDmAAC9IXch2Rk248.png "title=" Fabric.png "alt=" Wkiol1c6z0-tffdmaac9ixch2rk248.png "/>

Then the official document has a sentence:

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/80/30/wKioL1c6z8DAOZA9AAA1ToBui-o152.png "title=" fabric _backing_store. PNG "alt=" Wkiol1c6z8daoza9aaa1tobui-o152.png "/>

The problem is that since the backing store database (storage cluster configuration information) is so important, why isn't it designed to be highly available? The high availability of the business database, but also the introduction of a new single point, too confusing. Do you think that the backing store database is more stable than the production library, so you don't have to think about it hanging out? Backup alone is not enough, and as a highly available design, it is important to consider the overall impact of the problem on the production system.

This article is from the "Memory Fragments" blog, so be sure to keep this source http://weikle.blog.51cto.com/3324327/1774373

About MySQL Fabric