Craig had suggested how to modify the introduction. I think the suggestion
is pretty good:

Sharding-JDBC is an enhanced JDBC driver that provides in-process
> transparent distributed database by connecting to multiple database back
> ends. It supports many ORM frameworks and database connection pools and
> supports many back end databases that have JDBC interfaces: MySQL, Oracle,
> SQLServer and PostgreSQL.
> Sharding-Proxy is a database proxy that runs in a separate process and
> appears as a database server to multiple back end databases. It supports
> multiple client front ends such as MySQL Command Client, MySQL Workbench,
> Navicat etc. Current support is for MySQL and PostgreSQL.


Sheng Wu <[email protected]> 于2019年4月21日周日 下午8:38写道:

> This is the sentence I quote from our twitter
>
> > Open-source distributed database middleware for data sharding, read-write
> split and BASE transaction.
>
> Does this still fit us now?
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
> Sheng Wu <[email protected]> 于2019年4月21日周日 下午7:55写道:
>
> > Hi, everyone
> >
> > I want to start a discussion about how to introduce project in not more
> > than 4 sentences.
> > Besides discussion in incubator, I think this is clear for our project to
> > make landscape clear and re-usable in Conf, twitter etc.
> >
> > Any suggestion?
> >
> > Sheng Wu <[email protected]>于2019年4月21日 周日下午7:51写道:
> >
> >> Hi Liang
> >>
> >> The introduction is a little too long. One or two sentences for project
> >> description is good and clear for everyone.
> >> And be good for clear project landscape.
> >>
> >> Let's start a discussion in dev mail.
> >>
> >> [email protected] <[email protected]>于2019年4月21日 周日下午6:52写道:
> >>
> >>> Hi all,
> >>>
> >>> Apache ShardingSphere (incubating) Team is glad to announce the first
> >>> release of Apache ShardingSphere Incubating 4.0.0-RC1.
> >>>
> >>> ShardingSphere is an open-source ecosystem consisted of a set of
> >>> distributed database middleware solutions, including 2 independent
> >>> products, Sharding-JDBC & Sharding-Proxy.
> >>> They both provide functions of data sharding, distributed transaction
> and
> >>> database orchestration, applicable in a variety of situations such as
> >>> Java
> >>> isomorphism, heterogeneous language.
> >>> Aiming at reasonably making full use of the computation and storage
> >>> capacity of database in distributed system, ShardingSphere defines
> itself
> >>> as a middleware, rather than a totally new type of database.
> >>> 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.
> >>>
> >>> Sharding-JDBC defines itself as a lightweight Java framework that
> >>> provides
> >>> extra service at Java JDBC layer.
> >>> With client end connecting directly to the database, it provides
> service
> >>> in
> >>> the form of jar and requires no extra deployment and dependence.
> >>> It can be considered as an enhanced JDBC driver, which is fully
> >>> compatible
> >>> with JDBC and all kinds of ORM frameworks.
> >>>
> >>> * Applicable in any ORM framework based on Java, such as JPA,
> Hibernate,
> >>> Mybatis, Spring JDBC Template or direct use of JDBC.
> >>> * 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-Proxy defines itself as a transparent database proxy,
> providing
> >>> a
> >>> database server that encapsulates database binary protocol to support
> >>> heterogeneous languages.
> >>> Friendlier to DBA, the MySQL/PostgreSQL version provided now can use
> any
> >>> kind of client access (such as MySQL Command Client, MySQL Workbench,
> >>> Navicat etc.) that is compatible of MySQL/PostgreSQL protocol to
> operate
> >>> data.
> >>>
> >>> * Totally transparent to applications, it can be used directly as MySQL
> >>> and
> >>> PostgreSQL.
> >>>
> >>> * Applicable to any kind of compatible of client end that is compatible
> >>> of
> >>> MySQL and PostgreSQL protocol.
> >>>
> >>>
> >>> Vote Thread:
> >>>
> >>>
> https://lists.apache.org/thread.html/25c11b46dd3a58d4048dd35be71d21f86db6f5278480eb7083149af1@%3Cgeneral.incubator.apache.org%3E
> >>>
> >>> Download Links:
> >>>
> >>>
> https://dist.apache.org/repos/dist/release/incubator/shardingsphere/4.0.0-RC1/
> >>>
> >>> Release Notes:
> >>>
> >>>
> https://github.com/apache/incubator-shardingsphere/releases/tag/4.0.0-RC1/
> >>>
> >>> Website: https://shardingsphere.apache.org/
> >>>
> >>> ShardingSphere Resources:
> >>>
> >>> - Issue: https://github.com/apache/incubator-shardingsphere/issues
> >>> - Mailing list: [email protected]
> >>> - Documents: https://shardingsphere.apache.org/document/current
> >>>
> >>> ------------------
> >>>
> >>> Liang Zhang (John)
> >>> Apache ShardingSphere & Dubbo
> >>>
> >> --
> >> Sheng Wu
> >> SkyWalking, Shardingsphere and Zipkin
> >>
> > --
> > Sheng Wu
> > SkyWalking, Shardingsphere and Zipkin
> >
>


-- 
Zhang Yonglun
Apache ShardingSphere

Reply via email to