https://github.com/siveing/clean-architecture-nestjs
https://github.com/siveing/clean-architecture-nestjs
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/siveing/clean-architecture-nestjs
- Owner: siveing
- Created: 2024-05-22T04:37:17.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2024-05-23T11:38:19.000Z (11 months ago)
- Last Synced: 2025-01-16T21:24:16.343Z (4 months ago)
- Language: TypeScript
- Size: 136 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Description
[Nest](https://github.com/nestjs/nest) framework TypeScript starter repository.
## Installation
```bash
$ yarn install
```
## Migration
```bash
$ npm run typeorm_src migration:run
```
## Running the app
```bash
# development
$ yarn run start
# watch mode
$ yarn run start:dev
# production mode
$ yarn run start:prod
```
## BIO
Keeping learning new thing and implement it, not only thought it goods but NO ACTION.
Seem this structure change my mind too.
Good practice on something new at least, it gave ideas
## Reference
[Clean Architecture](https://medium.com/@chaewonkong/performance-disadvantages-of-clean-architecture-a-closer-look-1fe38362c74f) Pros and Cons of Clean Architecture
## MY Practice
- `Application`: The applications work as servcice and direct with repository by pasting the data to it, Such as MIDDLE WARE to paste action or not.
- `Domain`: This directory is used to manage the interfaces or we say it as TYPES manager to match with typescript
- `Infrastructure`: Many things in this folder within config, entities, and repositories. Most initial work in here and continue add the entity and repository by the requirement of the works.
- `Presentation`: Seem we have work many project on NestJs, It is simple structure to manage one folder within controller, service, and module. BUT this manage only controller and we can import service to interact with DB via use case repository
## HOW TO IMPLEMENT
1. First of all, You have to create module both `module` and `controller` in `Presentation`
2. Then, you can create your data interface or repository in `Doamin` that contain it boths
3. Next, you can implement the use case in `Applications/use-cases` to register your usecase actions
4. After you create your usecase, then have to register in `Infrastructures`/`usecase-proxy` in the module BUT you have to create your repository first by implement from `Domain` interface of repository
5. After all of this, you can work as normal within `Presentation` to implement your controller and service and combine to work with usecase in `Application` as their service with direct to model repository