feat: add dao layer #2276
Open
feat: add dao layer #2276
+308
−102
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TheoPascoli
force-pushed
the
feat/poc-add-dao-layer-v2
branch
2 times, most recently
from
41a8416 to
71e988b
Compare
TheoPascoli
force-pushed
the
feat/poc-add-dao-layer-v2
branch
from
71e988b to
c2413a9
Compare
TheoPascoli
force-pushed
the
feat/poc-add-dao-layer-v2
branch
from
c2413a9 to
24e826c
Compare
…sSimulatorTeam/AntaREST into feat/poc-add-dao-layer-v2
# Conflicts: # tests/variantstudy/model/command/test_create_link.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a second iteration of a previous one #2248 , which I'm about to close because it is too complex to modify.
I am implementing a DAO (Data Access Object) layer between the business layer (manager) and the storage layer. Additionally, I have implemented a caching logic to accelerate data retrieval, reducing the overhead of fetching frequently accessed data directly from the storage layer.
The goal is to create a clean separation of concerns, allowing the business logic to interact with the data through well-defined interfaces. This approach will make it easier to:
One of the next steps is to reverse the current behavior of the commands. Instead of having the StorageDAO call the commands, I want the commands to directly invoke the DAOs. This inversion will improve modularity and make the system more flexible to extend or modify in the future.
If you have suggestions or see potential improvements, feel free to share them