This issue proposes the separation of the DbProviders logic into a standalone project within our ASP.NET Core framework. The main goal is to enhance modularity and maintainability of our database interaction layers.
Rationale
Modularity: By separating DbProviders into their own project, we can achieve a more modular architecture, allowing easier updates and maintenance.
Reusability: This separation will enable the reuse of DbProvider logic across different projects without the need to duplicate code.
Maintainability: It simplifies the codebase, making it easier to manage and understand, especially for new team members.
Proposed Solution
Create a new project within the solution dedicated to DbProviders.
Refactor the existing DbProvider logic to be isolated within this new project.
Ensure that all existing functionalities are preserved and properly linked to the new project.
Impact on Existing Code
This change will require refactoring existing database access code to utilize the new project.
Careful consideration must be given to dependency management to ensure smooth integration.
Overview
This issue proposes the separation of the DbProviders logic into a standalone project within our ASP.NET Core framework. The main goal is to enhance modularity and maintainability of our database interaction layers.
Rationale
Proposed Solution
Impact on Existing Code