Service-based abstraction refactor #71
Description
The app is growing and we are beginning to feel the pains of not having a central location of truth for each domain and shared business logic. To address this, we should implement a service-based pattern to supplement the domain-driven organization of the codebase.
Attached is a plan that outlines an approach to implement the refactor. Each domain should be done separately or inclusive of domains that use a lot of the same logic. For example, the shared logic of history tracking touches multiple places. This can be done as a separate ticket. Each domain itself and be a separate ticket as well. This will help the scope of each ticket not be too large and it will keep everything from being refactored in one huge Pull Request.
I have suggested subtask tickets below but feel free to modify them as necessary.
domain-abstraction-patterns.md
Dev Time
- Reading and understanding docs - ET: 5hrs
Metadata
Metadata
Type
Projects
Status