Bee read write separation Usage Summary

Bee Read / write separation RW、 A master-slave mode
2 Read / write separation RW、 A master-slave mode
bee.dosql.multiDS.enable=true
# Data sources that support simultaneous use of multiple types of databases .
#bee.dosql.multiDS.differentDbType=true
#bee.dosql.multiDS.defalutDS=ds1

#write DB just set one db.
bee.dosql.multiDS.writeDB=ds1
#bee.dosql.multiDS.readDB=ds2,ds3
#poll:1, rand:2
#bee.dosql.multiDS.rDbRouteWay=1

Support scenarios :
Support horizontal extension from the Library , Flexibly adjust any flow proportion of each slave library
Support to preferentially select the nearest library to read data , Avoid cross room access
Flexible mandatory master database policy , Support single SQL Or all within the entire request SQL Go to the main library
The write library cannot be placed in the read-only library list   If you need to read data from the main library , Kertek
A transaction has both read and write operations , Is unified to the write library

Master slave synchronization , from DB be responsible for .

High availability problem . It mainly includes ：
newly added slave node ： If new slave node , Applications should be aware of , Read requests can be forwarded to new slave Node .
slave Down or offline ： If one of them slave The node is hung / Or it's offline , They should be isolated , Then the subsequent read requests , The application forwards it to a working slave Node .
master Downtime ： Need to switch between master and slave , Put one of them slave Upgrade to master, After the application, the write operation is transferred to the new master Node .
Find corresponding problems , Refresh the configuration information in time , And set the flag to update the context configuration :HoneyContext.setConfigRefresh(true);

improvement :
Provide nearest route 、 Current limiting and other functions .