3 replies

API layered architecture

Hi, I'm trying to apply the concepts of a layered architecture on a file upload API. Currently I have a folder structure that resembles this:

src
├── api
│   └── files
│       ├── file.controller.ts
│       ├── file.repository.ts
│       ├── file.router.ts
│       └── file.service.ts
└── index.ts

src
├── api
│   └── files
│       ├── file.controller.ts
│       ├── file.repository.ts
│       ├── file.router.ts
│       └── file.service.ts
└── index.ts

Inside

file.repository.ts

file.repository.ts

will be all functionality related to talking to the database. However, I intend to save the uploaded files on the server instead of using a 3rd party service for this, mainly for practice purposes. The question then is, where would this functionality (reading from and writing to disk) live? Inside services? Repository? Or should I create a whole new domain (maybe called

io

io

or something) just for this?
Cheers!

KP-C

Kevin Powell - Community•4y ago•

3 replies

Joao

API layered architecture

Hi, I'm trying to apply the concepts of a layered architecture on a file upload API. Currently I have a folder structure that resembles this:

src
├── api
│   └── files
│       ├── file.controller.ts
│       ├── file.repository.ts
│       ├── file.router.ts
│       └── file.service.ts
└── index.ts

src
├── api
│   └── files
│       ├── file.controller.ts
│       ├── file.repository.ts
│       ├── file.router.ts
│       └── file.service.ts
└── index.ts

Inside

file.repository.ts

file.repository.ts

io

io

or something) just for this?
Cheers!

API layered architecture

Similar Threads

API layered architecture

Similar Threads

Similar Threads

Similar Threads