In the research of various open source middleware, such as Ali Cobar/tddl, Mycat, official mariadb Spider, Qihoo Altas, official MySQL proxy/fabric, in function and performance, as well as maintenance costs, Oneproxy is more suitable for my business here.
Test + on-line, lasted one months, oneproxy run stable, solve the current my side of the connection pool, read and write separation (delay 1 seconds of slave automatic kick offline, forced to walk the main library). On the security side, through the Onefirewall white list mechanism greatly reduced the risk of SQL injection, the official MySQL5.7 although also implemented a firewall, but must buy Enterprise Edition, expensive, and not GA, can only be deterred.
My side of the top-up withdrawal business is the Java language, mybatis/springs framework, development has not changed one line of code, seamless migration.
In the Sub-database table, note that the cross-Library join is not supported, distributed transactions are not supported (Update Node 1 and Node 2 data, not supported), insert to add the field name.
video sharing Address: http://edu.51cto.com/index.php?do=lesson&id=31477
This article is from the "Spring Yang Technical column" blog, please be sure to keep this source http://hcymysql.blog.51cto.com/5223301/1671125
Oneproxy Middleware production use experience video sharing