Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

To decouple Sharding-Orchestration from Sharding-JDBC #1153

Closed
4 tasks done
tristaZero opened this issue Aug 16, 2018 · 0 comments
Closed
4 tasks done

To decouple Sharding-Orchestration from Sharding-JDBC #1153

tristaZero opened this issue Aug 16, 2018 · 0 comments
Assignees

Comments

@tristaZero
Copy link
Contributor

tristaZero commented Aug 16, 2018

For English only, other languages we will close it directly.
Please answer these questions before submitting your issue. Thanks!

Which version of Sharding-Sphere do you using?

3.0.0.M2

Which project do you using? Sharding-JDBC or Sharding-Proxy?

Sharding-JDBC

Analyze

We need to make sharding orchestration independent of sharding jdbc.

The tasks are as follows:

  • Set the API for OrchestrationDataSource.

Instead of using extend mode, it is better to use decorator mode to rewrite OrchestrationDataSource.

  • Move all source code of Orchestration and event code in Sharding-Core to Sharding-Orchestration.

  • Handle the orchestration of SP and S-JDBC by the same way.

  • Move refress, circutBreak, disabled functions from Sharding-JDBC to Sharding-JDBC-Orchestration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant