Hi All,
We have lots of rule about sharding, encrypt, master-slave, shadow,
replica, and maybe add more in future.
The current rule configurations are inconsist and scattered. I plan to
define the rule configuration level of them and to help user easy to
understand it.
The 1st level is rule, which include root configuration and some rule
config,for example: table rule with sharding, column rule with encrypt,
data source rule with master-slave...
The 2nd level is strategy, which for configure the main strategy of
sharding, encrypt or others.
The 3rd level is algorithm, which is provided by SPI only and
include concrete sharding or encrypt algorithm. The algorithm has no
relationship with data or database schema structure.
The Java API is look like:
```
RootRuleConfiguration
-- XXXRule
-- XXXSubRule1
-- XXXStrategy
-- XXXAlgorithmType
-- XXXSubRule2
-- XXXStrategy
-- XXXAlgorithmType
```
Any suggestions?
------------------
Liang Zhang (John)
Apache ShardingSphere
