Commit 0bf3cc93 authored by terrymanu's avatar terrymanu
Browse files

update readme

parent 226193fe

README.md

+5 −5
Original line number Diff line number Diff line
@@ -29,7 +29,7 @@ Aiming at reasonably making full use of the computation and storage capacity of 
As the cornerstone of many enterprises, relational database still takes a huge market share. 

Therefore, at current stage, we prefer to focus on its increment instead of a total overturn.



![ShardingSphere Scope](http://ovfotjrsi.bkt.clouddn.com/sharding-sphere-scope_en_v2.png)

![ShardingSphere Scope](http://shardingsphere.jd.com/document/current/img/shardingsphere-scope_en.png)



### Sharding-JDBC
@@ -43,7 +43,7 @@ It can be considered as an enhanced JDBC driver, which is fully compatible with 
* Based on any third-party database connection pool, such as DBCP, C3P0, BoneCP, Druid, HikariCP.

* Support any kind of database that conforms to JDBC standard: MySQL，Oracle，SQLServer and PostgreSQL for now.



![Sharding-JDBC Architecture](http://ovfotjrsi.bkt.clouddn.com/sharding-jdbc-brief.png)

![Sharding-JDBC Architecture](http://shardingsphere.jd.com/document/current/img/sharding-jdbc-brief.png)



### Sharding-Proxy
@@ -56,7 +56,7 @@ Friendlier to DBA, the MySQL version provided now can use any kind of client acc 
* Totally transparent to applications, it can be used directly as MySQL.

* Applicable to any kind of compatible of client end that is compatible of MySQL protocol.



![Sharding-Proxy Architecture](http://ovfotjrsi.bkt.clouddn.com/sharding-proxy-brief_v2.png)

![Sharding-Proxy Architecture](http://shardingsphere.jd.com/document/current/img/sharding-proxy-brief_v2.png)



### Sharding-Sidecar(TBD)
@@ -68,7 +68,7 @@ Focusing on interaction, it effectively organizes the interaction between messy 
The application and database that use Database Mesh to visit database will form a large grid system, where they just need to be put into the right position accordingly. 

They are all governed by mesh layer.



![Sharding-Sidecar Architecture](http://ovfotjrsi.bkt.clouddn.com/sharding-sidecar-brief_v2.png)

![Sharding-Sidecar Architecture](http://shardingsphere.jd.com/document/current/img/sharding-sidecar-brief_v2.png)



|                         | *Sharding-JDBC* | *Sharding-Proxy*     | *Sharding-Sidecar* |

| ----------------------- | --------------- | -------------------- | ------------------ |
@@ -112,4 +112,4 @@ Architects can adjust the system architecture to the most applicable one to curr 


## Roadmap



![Roadmap](http://ovfotjrsi.bkt.clouddn.com/roadmap_en_v3.png)
 
![Roadmap](http://shardingsphere.jd.com/document/current/img/shardingsphere-roadmap_en.png)

README_ZH.md

+5 −5
Original line number Diff line number Diff line
@@ -30,7 +30,7 @@ ShardingSphere定位为关系型数据库中间件，旨在充分合理地在分 
ShardingSphere目前已经进入[Apache孵化器](http://incubator.apache.org/projects/shardingsphere.html)，

欢迎通过[shardingsphere的dev邮件列表](mailto:dev@shardingsphere.incubator.apache.org)与我们讨论。



![ShardingSphere Scope](http://ovfotjrsi.bkt.clouddn.com/sharding-sphere-scope_cn.png)

![ShardingSphere Scope](http://shardingsphere.jd.com/document/current/img/shardingsphere-scope_cn.png)



### Sharding-JDBC
@@ -43,7 +43,7 @@ ShardingSphere目前已经进入[Apache孵化器](http://incubator.apache.org/pr 
* 基于任何第三方的数据库连接池，如：DBCP, C3P0, BoneCP, Druid, HikariCP等。

* 支持任意实现JDBC规范的数据库。目前支持MySQL，Oracle，SQLServer和PostgreSQL。



![Sharding-JDBC Architecture](http://ovfotjrsi.bkt.clouddn.com/sharding-jdbc-brief.png)

![Sharding-JDBC Architecture](http://shardingsphere.jd.com/document/current/img/sharding-jdbc-brief.png)



### Sharding-Proxy
@@ -56,7 +56,7 @@ ShardingSphere目前已经进入[Apache孵化器](http://incubator.apache.org/pr 
* 向应用程序完全透明，可直接当做MySQL使用。

* 适用于任何兼容MySQL协议的的客户端。



![Sharding-Proxy Architecture](http://ovfotjrsi.bkt.clouddn.com/sharding-proxy-brief_v2.png)

![Sharding-Proxy Architecture](http://shardingsphere.jd.com/document/current/img/sharding-proxy-brief_v2.png)



### Sharding-Sidecar（TBD）
@@ -66,7 +66,7 @@ ShardingSphere目前已经进入[Apache孵化器](http://incubator.apache.org/pr 
Database Mesh的关注重点在于如何将分布式的数据访问应用与数据库有机串联起来，它更加关注的是交互，是将杂乱无章的应用与数据库之间的交互有效的梳理。

使用Database Mesh，访问数据库的应用和数据库终将形成一个巨大的网格体系，应用和数据库只需在网格体系中对号入座即可，它们都是被啮合层所治理的对象。



![Sharding-Sidecar Architecture](http://ovfotjrsi.bkt.clouddn.com/sharding-sidecar-brief_v2.png)

![Sharding-Sidecar Architecture](http://shardingsphere.jd.com/document/current/img/sharding-sidecar-brief_v2.png)



|           | *Sharding-JDBC* | *Sharding-Proxy* | *Sharding-Sidecar* |

| --------- | --------------- | ---------------- | ------------------ |
@@ -108,4 +108,4 @@ ShardingSphere是多接入端共同组成的生态圈。 


## Roadmap



![Roadmap](http://ovfotjrsi.bkt.clouddn.com/roadmap_cn_v2.png)
 
![Roadmap](http://shardingsphere.jd.com/document/current/img/shardingsphere-roadmap_cn.png)