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, routes, services, repository, etc have been added in their separate folders.
This make it less modular, harder to re-use and less maintainability.
Thinking of making this structure something like this;
pkg
|-- authentication (model, handler, service, route, repository, serializer etc.)
|-- users
|-- ....
|-- common (some common things re-usable by multiple modules)
internal
|-- framework's internal wiring code
domain
|-- users.go (interfaces for users package)
|-- authentication.go (interfaces for authentication package)
While we are at it, we need to look at the go's recommended folder structure for packages.
Following something like this
The text was updated successfully, but these errors were encountered:
Modular Folder Structures
Currently, routes, services, repository, etc have been added in their separate folders.
This make it less modular, harder to re-use and less maintainability.
Thinking of making this structure something like this;
While we are at it, we need to look at the go's recommended folder structure for packages.
Following something like this
The text was updated successfully, but these errors were encountered: