Skip to content

Separate Business Logic from Routes #88

Open
@josh-byster

Description

@josh-byster

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

As our application is growing now more complex with our business logic, our routes are becoming more packed with handling different scenarios and doing a lot in the route handler. It becomes difficult at that point to take pieces and reuse them in other route handlers.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Extracting out all this business logic in our backend to a "service" layer as described here. This way, we have a separation of concerns and encapsulation of logic into different pieces which we can test and reuse throughout our code.

Additional context
Add details, any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions