Hi Liang,
The Plan B looks like similar to the netty pipeline architecture and will
be much more flexible.
Regards,
Zheng Feng
zhangli...@apache.org 于2020年1月3日周五 上午12:13写道：
> I have 2 ideas for the pluggable platform.
>
> Plan A:
>
> Design a unify DataSource to process all rules, it should
: zhangli...@apache.org
发送时间: 2020年1月3日 0:13
收件人: dev@shardingsphere.apache.org
主题: Re: Discussion of pluggable platform of ShardingSphere
I have 2 ideas for the pluggable platform.
Plan A:
Design a unify DataSource to process all rules, it should be a transparent
DataSource if no rule provided
I prefer Plan A too.
--
Yi Yang(Sion)
Apache ShardingSphere
At 2020-01-03 00:13:07, "zhangli...@apache.org" wrote:
>I have 2 ideas for the pluggable platform.
>
>Plan A:
>
>Design a unify DataSource to process all rules, it should be a transparent
>DataSource if no rule provided (but
I have 2 ideas for the pluggable platform.
Plan A:
Design a unify DataSource to process all rules, it should be a transparent
DataSource if no rule provided (but it should be valid). We can name it as
`ShardingSphereDataSource`.
There are lots of hooks in `ShardingSphereDataSource`, such as:
-
+1 It sounds great.
And is the platform suitable for JDTX? And Sharding may not be a necessary
function, maybe transaction will be more widely used. So, will JDTX will be
a plugin which is easily used in the platform?
Zonglei Dong 于2019年12月9日周一 下午9:24写道：
> +1, That sounds great!
>
>
> For a
+1, That sounds great!
For a pluggable platform, contributors will be very convenient to contribute
code, This will attract more people.
Zonglei Dong
Apache ShardingSphere
On 12/9/2019 19:13，sunbufu wrote：
+1
Good idea. It’s a good long-term planning for ShardingSphere.
—
+1
Good idea. It’s a good long-term planning for ShardingSphere.
—
Haisheng Sun (sunbufu)
Apache ShardingSphere
On 12/9/2019 18:43，Juan Pan wrote：
Agree with Liang,
Maybe there is no feature benefit apparently, however we make its architecture
become…a structured plaza with many
Agree with Liang,
Maybe there is no feature benefit apparently, however we make its architecture
become…a structured plaza with many rooms. Consequently, more contributors
could fill in specific implements for those rooms with less harms to this
plaza, i.e our project. Oh, i have a great
+1
Pluggable data platform would be a brand new start.
Looking forward to combining variety powerful features through SPI, not just
inside the sharding-core.
--
Zhao Jun (cherrylzhao)
Apache ShardingSphere & ServiceComb
> On Dec 9, 2019, at 1:29 PM, zhangli...@apache.org
Hi,
> What features will be planned in pluggable platform?
There is no new feature of pluggable platform. We just need redesign the
current framework to make it more flexible.
> And how to assign features splits from sharding-core?
As the new design, sharding-core is not a mandatory feature,
> +1 Love the idea. Just feeling the project name(Sharding) will be the
bottleneck :P
Sharding is a brand of previous name (Sharding-JDBC), because JDBC is not
suitable with our project, so we keep the first word as brand and just
change the last word to `Sphere`.
Maybe we can talk about change
+1 Love the idea. Just feeling the project name(Sharding) will be the
bottleneck :P
Sheng Wu 吴晟
Twitter, wusheng1108
zhangli...@apache.org 于2019年12月9日周一 下午1:30写道：
> Hi, ShardingSphere community,
>
> More and more features are added into ShardingSphere now, as you know, the
> scope of
Hi, ShardingSphere community,
More and more features are added into ShardingSphere now, as you know, the
scope of ShardingSphere is no longer for sharding only.
There are more and more features related with sharding, such as distributed
transaction, distributed orchestration, observability and so
13 matches
Mail list logo
