You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in the flux codebase, the resource and controller classes interact with DAO layer directly. This lacks good coding practices such as separation of concerns, extensibility, and readability. One way to solve this problem would be to introduce a persistence layer that would handle all the transactions by interacting with DAO layer. The communication would be like below with the new model.
Resource --> Controller --> Persistence Layer --> DAO layer
The text was updated successfully, but these errors were encountered:
Currently, in the flux codebase, the resource and controller classes interact with DAO layer directly. This lacks good coding practices such as separation of concerns, extensibility, and readability. One way to solve this problem would be to introduce a persistence layer that would handle all the transactions by interacting with DAO layer. The communication would be like below with the new model.
Resource --> Controller --> Persistence Layer --> DAO layer
The text was updated successfully, but these errors were encountered: