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

Will EFCcore support sharding and table sharding in the future? Similar to Java's ShardingSphere #31145

Open
softchar opened this issue Jun 27, 2023 · 6 comments

Comments

@softchar
Copy link

No description provided.

@ajcvickers
Copy link
Contributor

@softchar No support specific to EF Core is planned.

@Varorbc
Copy link
Contributor

Varorbc commented Jun 28, 2023

I really hope the plan supports this feature

@ajcvickers
Copy link
Contributor

@softchar In your mind, what would sharding support in EF look like? What would it do?

@Varorbc
Copy link
Contributor

Varorbc commented Jul 9, 2023

@roji
Copy link
Member

roji commented Sep 12, 2024

@Varorbc and others, if what you're looking for is already implemented in sharding-core, then what's the reason for asking for this to be implemented inside EF? We very much believe that EF should be as extensible as possible, and that things that can be built outside of EF itself should be built as plugins/extensions. It is unfeasible for EF to have built-in support for everything.

@roji
Copy link
Member

roji commented Sep 12, 2024

EF is more reassuring and the technical support is very good.

We have had many requests over the years, where a perfectly good plugin/extension exists, and yet people ask us to implement it in-the-box simply because "it's better inside EF". We generally say no to these; it's simply unfeasible for one product - and one team - to implement everything database-related that could be imagined, and where external plugins can exist which implement the functionality, that's the best possible situation in our view.

I'll keep this open in the backlog to track user interest and possibly discuss details, but overall I don't see us going in this direction unless specific, compelling reasons are brought forth as to why this needs to exist inside EF itself.

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

4 participants