EF Core data access / ORM plugin
A plugin for Microsoft.EntityFrameworkCore that adds repository and unit-of-work patterns, distributed transactions across multiple databases, and MySQL sharding.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Same .NET EF Core stack, adds auto-history and QueryBuilder beyond the seed's UoW/repository.
It's a modern and generic data access structure for .NET and Microsoft.EntityFrameworkCore. It supports UnitOfWork, Repository and QueryBuilder patterns. It also includes auto history utilities, multiple databases support with distributed transactions and databases/tables sharding for some database providers.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose it when you need MySQL sharding as a standalone proxy, not an in-process EF Core library.
a proxy for sharding databases and tables
Choose it for a broader distributed SQL ecosystem with sharding, scaling, and security, but as a Java proxy, not an EF Core plugin.
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
Choose it when you need distributed transactions and sharding as a language-agnostic sidecar proxy.
A db proxy for distributed transaction, read write splitting and sharding! Support any language! It can be deployed as a sidecar in a pod.
Choose it for MySQL sharding as a standalone Java middleware.
A High Scalability Middle-ware for MySQL Sharding
Choose it for distributed transactions as a standalone multi-language framework instead of an EF Core plugin.
A distributed transaction framework, supports workflow, saga, tcc, xa, 2-phase message, outbox patterns, supports many languages.
Choose it for MySQL sharding as an older Java middleware, not an EF Core library.
:shark:分布式mysql分库分表中间件，sharding领域的一站式解决方案
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Choose it if you only need EFCore sharding, but it lacks the seed's UoW/repository and distributed transaction features.
Database Sharding For EFCore
These projects were analysed and named UnitOfWork among their alternatives. The relationship is not symmetric — how UnitOfWork rates them is a separate judgement, made when UnitOfWork is analysed in its own right.
calls UnitOfWork “Choose only for legacy EF Core projects needing client-side sharding; it is a stale ORM plugin.”
A high-performance MySQL proxy